I have 2 entities Entity A & B.
In Entity A, I have created a form. In this form I want to add a Grid Type Control which will have Add button to add Records from Entity B.
I am new to this CRM 2013 form making. Tried searching over internet but no luck.
Thanks
Here are some keywords to get you started:
You want to create a 1:N-relationship between Entity A and Entity B
Then you want to add a sub-grid of Entity B-records to Entity A's form.
This video walks through adding a sub-grid to a form.
Related
I need to know how to set which form to open when we click on the +New button in lookup fields in an entity form in microsoft dynamics crm.And is it possible that we can populate quick create form fields based on a form field ,on which the lookup field from which the quick create form was opened, is present?
There is no way to configure which Quick Create form to use depending on the field you start from our which button you press or any other client-side code. Only one Quick Create form can be used per entity.
It might be a good suggestion for http://connect.microsoft.com (if it is not already there).
I got the solution for opening quick create form.
We can set it by setting the following properties to the lookup field.
document.getElementById("lookupfieldname").setAttribute("entitylogicalname", "nameofentityyouwanttoset");
document.getElementById("lookupfieldname").setAttribute("entitytypecode", "codeforthatentity");
But I need to know that is it possible that we can populate quick create form fields based on a form field of the form on which the lookup field,from which the quick create form was opened, is present?
I have created a form for use during a meeting. Multiple people need to click approve at the same time. The issue is if they all are in the form at the same time, it is only going to keep the last approval and resets the fields the others have approved... as there approval was not there when the form was opened. I guess I should have seen this coming. Is there anything I can do?
Use two lists with a parent/child relationship.
You need a master list with a unique ID and a detail list where the Master ID is assigned to the new list items to define the relationship. In the Master List you can customize the display form to contain a list view of the related items in the Detail list and a link to add new items to that detail list. A little bit of JavaScript will ensure that a new item in the Detail list gets the Master item's ID assigned automatically.
Clear as mud? The SharePoint Hillbilly has a video tutorial for 2007 and 2010.
If you go through the material (the 2007 stuff is good to understand the approach), you'll find that there are two techniques, one using SharePoint Designer, the other one without SPD.
Back to your meeting: Before the meeting, create an item in the Master list. Everybody can see the item on their screen and click to create a related item in the Detail list. They can all save their related item at the same time, since these are individual list items in the Detail list. Refresh the display view of the Master list item to see everybody's replies.
I want to create dropdown list using ASP.NET MVC4 and Entity Framework is used for database connectivity.
Problem is that I want create a new department name item in this dropdown list when click on it a javascript prompt is open with text box and ask for new department from end user. where he/she can add new department with his own desire and this is store in database and show in dropdown list after save.
I have designed a user control in Visual Studio 2013 (VB) . The control contains three Combobox controls through which user can select different values. I bind each combobox to a specific table field in my database (SQL Server) through assigning each combobox's properties [DataSourse, DisplayMember, and ValueMember] the required values. I already created a DataSet.
When I add multiple instances (about 26) of my user-control to a form and run the application, the comboboxes SHOW nothing! as if they are empty. To make sure, I added a Combobox control on the form itself (where user-control instances added), and bind it the same way above, and .. mmm it works!
I'm not able to explain the reason behind this strange behaviour.
I appreciate any assistance.
I am developing a helpdesk system on sharepoint 2010 for our facility management dept., through which the call agent can log the client's complain through tickets. I have created 3 dropdown lists (asp.net controls from sharepoint designer) in the helpdesk page, reading repectively from our database the "projects", "properties" and "units", and the call agent will select the appropriate choice accroding to the client.
I have created a custom list, it is the helpdesk tickets, and edited its layout in infopath 2010.
I am displaying that list on the same page, but filtered according to the selected unit from the "units" dropdown list, to display the tickets history for that particular unit.
What I need is to set the default value for the "unit" field in the new ticket after the call agent clicks "add new item", to be the value selected in the "units" dropdown list.
I have tried a workaround, by removing those 3 controls and creating a new custom list and called it "engine", and edited its form to have the 3 dropdowns, then adding it as a data source for the ticket form, and displaying the "engine" form on the page.
The value of the unit was passed succesfully, but of course I have to click "save" after I enter the choices for the three dropdowns in that "engine" form for the value to be saved and passed to the "new ticket" form. also it was so much slower and the history filter was not working.
So I need to return to the first solution and keep the 3 asp.net dropdowns, and pass the sleected value of the "units" dropdown to teh "unit" field in the ticket form.
Thank you all in advance :)
I don't think it's possible to inject values into an IP Form. However, consider this workaround:
You create the "projects, "properties" and "units" dropdown's within InfoPath and then map this properties to the SharePoint list. This way, you can still apply SharePoint's default filter/group by/etc behaviour and you actually don't need to code anything yourself :-)