I have a subject tree as a case type on Case Entity
I want to display different subject rows in different Forms.
Like Form1 will display 'Client Services' and Form 2 will display say 'Credit' & 'Default Subject'.
Is it possible to do that?
Or Is there a way to apply a view to this field?
Subject field is very limited in nature. Probably you have to think in PCF controls direction.
Some community tree controls and source code available in PCF gallery, otherwise you can start a fresh control development.
Related
I'm new to customizing dynamics CRM, and I need to implement a custom form with a list that lets you add and remove "fruits" for a fruit store. To better illustrate what I need, I've attached a photo
I have "x" number of fruit types in a fruit store. The list of fruits can be managed and changed via the store owner. I want to be able to click add, choose a fruit from a list of fruits, then specify an amount, and have it update a total.
I want this in a form for an entity like Opportunity. Where do I begin with this level of customisation?
Does it involve creating a custom silver light control? Or is there something out of the box?
By default you don't have anything to accomplish that. To extend user interface of CRM you have recurring to WebResource, there is two types of WebResources that you can explore html or Silverlight. For me the best option is Silverlight.
You have some generic examples here:
http://blogs.msdn.com/b/crminthefield/archive/2011/06/23/how-to-create-a-silverlight-web-resource-that-interacts-with-crm-2011-forms.aspx
http://msdn.microsoft.com/en-us/library/gg328358.aspx
You have some examples of grids:
http://ankit.inkeysolutions.com/2013/01/crm-2011-lookup-functionality-in.html
If you need interact with CRM Database:
http://msdn.microsoft.com/en-us/library/gg309558.aspx
http://community.dynamics.com/product/crm/crmtechnical/b/crminogic/archive/2011/07/27/json-and-silverlight-with-odataservice-in-crm-2011.aspx
Nowadays the technology used would be editable grids, javascript. Silverlight is dead.
I am looking for People Picker Control similar to SharePoint one for MVC3 applications.
Can you please suggest if there are any such controls available?
What is the best approach to pick the people from AD in MVC3?
Requirement: On one of the Views, I need to select a user from AD.
I was thinking about People Picker kind of control.
Thanks
Arun
I know this is quite old so I doubt you still need this answered but perhaps it will be useful to someone else.
Just last week I had to build a control like does this for us. It's basically two main parts, a JSON service that accepts partial text and returns a list of suggestions and the HTML/CSS/jQuery+UI control.
The service is pretty straightforward so we'll skip over that here.
I'm in the process of doing a write-up on the web side but basically we wrapped the jQuery autocomplete with some custom CSS to make an input that is similar to the address line in GMail. This was done by styling a container div to look like a long input field. The actual input field is within that container and styled to be essentially invisible. Clicking in the container moves focus to the input box. Upon selecting a suggested name, I create a new container to insert before the 'cloaked' autocomplete input which contains the user name and a hidden input with our desired value to send along when the form is submitted. I had to do some other overloads on the autocomplete to get it to act consistently but essentially this is all there was to it.
The control looks at the container for a data-input-name attribute to figure out what 'name' to set the hidden inputs to when they are created with each user pick. When the form is submitted the default model binder rolls all the users of a particular picker (since you can have multiple on a page) into string arrays of the values - assuming your model has string array properties with the same name as used by the input controls - which we can then process on the server side.
By far the hardest part was figuring out the right HTML + CSS to get the look and feel right. I'm not a very strong UI person so this took me forever and still falls down in Chrome which seems to add an accent around input boxes even with (or because of?) styles which make it blend into the parent control.
For our purposes it's been working great over the last week.
UPDATE: It's now on GitHub with a Demo.
could someone help me with design/understanding the problem: what I need to achieve is page with Panorama/Pivot control, where its items (panos/pivots) will be set via binding, using standard MVVM pattern. Problem is I need to have different content (different user controls) on each pano/pivot, that means If I define a panorama/pivot item template, I doom all of them to be alike, which is not what I want.
I found this question here already asked: Databound windows phone panorama with MVVM design but its still not clear to me. Many thanks.
If you have a dynamic page count on panorama/pivot you could use selector to choose what template is right according to your content.
Implementing DataTemplateSelector
Also, Data Binding Pivot to MVVM may help you too
You could add a dependency property to the user control that you want to use as a data template, a dependency property named "Type" for example and depending on that property you can change the layout of your user control (data template) - for example you could have multiple grids inside your user control and you could show and hide them depending on the type.
CRM 2011 online. I have a requirement to color code entries that appear in an entity view. On a form for entity A is a field that is a lookup to entity B. Entity B has > 1 views defined for it. The lookup field on form A defines what view of entity B appears when the lookup button is pressed. I have been asked if the view that appears can show the records such that the entries are color coded based on a column value of the view e.g. if a record in the view has a value of X for a particular column, show that record with a green background, else show with a red. The view in question is a "public" view and is unmanaged and customizable.
In effect what I am asking is if it's possible to manipulate the display of that view somehow? If not, is the only other option to override the clicking of the lookup on the form for entity A and display my own custom view window?
What I have found in my searching is this which seems to suggest that I can export a view and manipulate the XML to incorporate some kind of conditional formatting. However, all it tells me is that the value is a string. Anyone have any experience there?
You are going to make it harder on yourself by having unmanaged code in your solution.
That being said, you can easily do this sort of thing in an iFrame or Silverlight control.
A quick google brought up some examples on how to do this.
This is my first time building a UI in Access (using Access 2007), and I'm wondering what is the Right Way (TM) of going about this.
Essentially, I have several different queries that I'd like to display as pivot charts, pivot tables, tables, and reports. Eventually I'm also going to have to build forms to manipulate the data as well, but the application's primary function is to display data.
I'm thinking of having a button for each different display down the left side of the main window, and having the rest of the window display each button's corresponding contents (e.g. a pivot chart).
I have an idea that this can be accomplished using a single subform in the main form, and setting the subform's Source Object property within a function such as this one:
Public Function SetSubformSourceObject(newSourceObject) As Variant
subform.SourceObject = newSourceObject
End Function
Then, for each button I'd set its OnClick property to call this function with the name of the query I'd like to run.
Now, I have no idea if this is the best way of going about things, and would really appreciate some input :)
The principle seems fair to me. You have to give it a try. You do not even need a form-subform structure. You can set your sourceObject at the form level, and have your buttons in a commandBar instead of having them as controls on the form, so you do not have any 'form specific' code (like "onCLick") and controls. action/command controls on a form are space, code and maintenance consuming, while commandbars are more generic and are THE object that can hold all your action controls.