It’s possible to get related records of a relationship when we retrieve a parent record using RelatedEntitiesQuery property in the RetrieveRequest. That means you have to construct the RetrieveRequest not using the Retrieve method from the OrganizationServiceProxy class.
by Khoa Nguyen
Continuing our previous example, here we have added a new choice field in Table B.
Here Table A has a lookup of Table B which has the new multichoice column added to it. (Also Table B has a lookup of Table C in it)
Based on the values selected in the multiple-choice field’s combo box we will filter the gallery.
The syntax to bind the multichoice column to the combo box.
Choices(Table[@choicecolumn])
First, for the Items property of the Main Gallery, we have added the new column ColorChoices to Table A using the AddColumns and the Lookup function.
Then filtered based on selected items of the combo color choices, using the new ColorChoices column added.
ChoiceColumn[@Value] in comboBox.SelectedItems
We have also used the newly added ColorChoices column to bind it to the gallery inside the main gallery as it would have multiple values.
The result –
Thanks to –
Hope it helps..
Suppose we have 3 tables, Table A, Table B, and Table C related to each other as
Table A (n-1) Table B (n-1) Table C i.e.
Table A has a lookup of Table B and Table B has a lookup of Table C.
Below is our sample canvas app that has a gallery and a combo box.
What we would want is based on the Table C record’s name selected in the combo box, we want to filter the collection to only show those records that are related to it.
One of the ways we could implement this is by using the AddColumns to add Table C data to Table A and apply the Filter to it.
Below is the formula to achieve the same.
In Table A, add a column name “TableCName”.
To get the Table C name, perform a Lookup on Table B, where Table B GUID is equal to Table A’s Table B lookup field, and then fetch the Table C Lookup’s name from Table B.
And lastly, perform a Filter on this new column TableCName, based on the selected value in the combo box.
See it working –
https://www.screencast.com/t/XZNDEsykAw
On selecting Table C1 in the combo box –
Similarly on selecting Table C2 in the combo box
Thanks to Debajit for guiding – https://debajmecrm.com/how-to-use-addcolumns-with-lookup-fields-of-sharepoint-in-power-apps/
To read more on AddColumns, Filter, and Lookup.
Hope it helps..
Product Table has Village Lookup in it and Village table has Region lookup in this sample screenshot
We might get the below error while using Xrm.WebAPI.
‘Bad Request – Error in query syntax.’
One of the reasons could be that while setting up the Lookup field, we haven’t removed the curly brackets.
Use the below function to replace/remove them.
Hope it helps..
Instead of hardcoding Combo box , we can bind it to the Choice / Option Set field of Dynamics 365 / Dataverse.
Format – Choices(DataSource[@columnname])
Check out the post that explains it – https://debajmecrm.com/how-to-bind-a-multiselect-choice-of-dataverse-to-a-combobox-in-canvas-apps/
Also check out – how to bind and do filter on multiselect combo box – https://youtu.be/5dSk5iOgT68?t=286
To learn about all the properties of Combo box refer – https://www.spguides.com/powerapps-combobox-control/
Hope it helps..
Here we will be cloning the below contact record –
For it, we can make use Clone method of EntityExtensions class
If we run the below code, we will get the “Cannot insert duplicate key” exception.
Because we need to set the ID for the newly cloned record to either empty or a new GUID.
Also, we need to remove the contactid attribute or entity’s id field else we will get the below exception – “Entity Id must be the same as the value set in property bag“
Also if we are retrieving all the attributes we need to make sure we remove those attribute which can cause below unique constraint errors.
Sql error: The operation attempted to insert a duplicate value for an attribute with a unique constraint. CRM ErrorCode: -2147012606 Sql ErrorCode: -2146232060 Sql Number: 2627
In case of contact, we had to remove the address id attributes, to get the record cloned.
Now let us clone the same contact record with its related leads.
Please refer the helpful posts –
https://debajmecrm.com/clone-record-dynamics-crm-clone-method/
https://www.inogic.com/blog/2014/08/clone-records-in-dynamics-crm/
https://dynamict.eu/2016/08/09/create-record-with-related-records-in-a-single-request-using-c/
Hope it helps..
// related lead records of contact
QueryExpression query = new QueryExpression("lead");
query.ColumnSet = new ColumnSet(true);
// contact and lead - 1 - n relationship
Relationship relationship = new Relationship("lead_parent_contact");
relationship.PrimaryEntityRole = EntityRole.Referenced;
RelationshipQueryCollection relatedEntity = new RelationshipQueryCollection();
relatedEntity.Add(relationship, query);
RetrieveRequest request = new RetrieveRequest();
request.RelatedEntitiesQuery = relatedEntity;
request.ColumnSet = new ColumnSet(true);
request.Target = new EntityReference("contact", new Guid("ca0aa844-57c6-ec11-a7b6-00224826af1e"));
RetrieveResponse response = (RetrieveResponse)svc.Execute(request);
var contactToBeCloned = response.Entity;
var clonedContact = contactToBeCloned.Clone(true);
// remove attribute that can cause error from main entity
clonedContact.Id = Guid.NewGuid();
clonedContact.Attributes.Remove("contactid");
clonedContact.Attributes.Remove("address1_addressid");
clonedContact.Attributes.Remove("address2_addressid");
clonedContact.Attributes.Remove("address3_addressid");
// remove attribute that can cause error from child / related entities
foreach (var relatedEntities in clonedContact.RelatedEntities)
{
foreach(var leadEntity in relatedEntities.Value.Entities)
{
leadEntity.Id = Guid.NewGuid();
leadEntity.Attributes.Remove("leadid");
leadEntity.Attributes.Remove("address1_addressid");
leadEntity.Attributes.Remove("address2_addressid");
}
}
svc.Create(clonedContact);
Nishant Rana's Weblog 