Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have created a LogicApp to pull data from CosmosDB and send to CRM. All of my fields cross over except the "lookup" fields.
Any field that has this:
My question, is how would I implement this in the Logic App?
Just doing this does not work, even when I add quotes.
The Feature Category that I pulled from CosmosDB already has a value:
My dilemma is:
How can I get this 'lookup' field to accept my value within the LogicApp?
Any help or suggestions are appreciated.
Based on the string value which you are getting from cosmos, you will need to use list record to get the record ID based on this field value in dynamics. You need to add filter in list record action.
Once you get the Record ID from above action. you need to pass the value as below for lookup field.
replace contacts with your entity name
see below article for your reference.
Ok thank you. Kindly help because I am searching for the field I'd like to update, but am unsure what to do next:
I do not understand this filter here. Am I supposed to be filtering for an id??
The lookup fields display the name of the record, but they actually store the ID in the field.
Your Feature Category field is lookup field, but you give it text in Parse Json.
You should put that Id in your field and it should automatically display name of Feature Category.
The ID ca be hardcoded to fill this field, like this(This is just an example):
Or if you also use list record to get record ID by set filter:
Entity that you list records is not current entity, which is primary entity of lookup field.
The filter query you can set as: Feature Category eq ‘Azure Stack’.
You can refer following to set filter:
Thank you so much Leah! You have been extremely helpful in helping me to understand. When you say that:
''You should put that Id in your field and it should automatically display name of Feature Category.'
What Id are you referring to? Where would I find this Id?
Here is my Feature Category field, but I do not see any Id appear in this field:
Am I doing something wrong? Afterwards, when I find this Id, where do I place it? here?:
Thank you for all of your help
Does this filter appear correct?
I don't think this filter criteria and entity name is correct.
Navigate to settings->Customization->Customize the system->Entity>Feature->Fields->Open Feature group fields->Check Target Record Type
Now go back to list record in logic apps change the entity name to same as Target record type in field property.
For filter criteria you should install below rest builder solution on your crm instance/you can also use fetchxml builder from xrm toolbox to build the filter criteria syntax.
Download managed solution and install in your crm instance.
build the filter criteria in rest builder and copy same in logic apps
I think your filter criteria should be new_name eq 'Azure Stack' --Replace new_ with your prefix
The ID is the GUID of the record that entity related to Feature entity by lookup field.
A lookup field is created by relationships between two entities, one is Feature that you mentioned, another entity about Feature category that you don’t mentioned, which record GUID is we need.
So you can’t use Feature entity, related entity is you need and field as filter must be the logical name of the related entity.
In my example, I named the related entity with Feature category.
You just fill the Guid to the lookup field.
I would first check if your CosmosDB has the record ID (GUID) of the Feature Category, if it does, you do not have to query CRM (CDS/Dataflex Pro) again. How did your CosmosDB get the data, it might be easy to update that integration to save the GUID along with text value in CosmosDB.
If the above is not feasible, like Bipin suggested you have to do a List Record (Retrieve Multiple) using the string value as a filter to find the record and then get the record from the results and use ID from that in your Create action.
Hi Bipin thank you for your input. I will try this today. Let me ask, what application are you in when you are:
‘ Navigate to settings->Customization->Customize the system->Entity>Feature->Fields->Open Feature group fields->Check Target Record Type’
Is this within Cosmosdb?
I will try this today and see if this works. Thank you
Ok thank you Leah. What application are you in when here?
I will try this today. Thank you very much
Ok thank you kindly. How would I check if my Cosmosdb has this record ID? Would I follow the above steps that Bipin and Leah suggest?
Thank you for your help
This is Dynamics CRM Application.
Replace CRMORG with your CRM instance.
You could use the CosmosDB data explorer and see if the the record id is stored in CosmosDB
Thank you. I will try all of this today. Thank you
The page is lookup field that named feature category page in the CRM..
After go into crm, you can Navigate to settings->Customization->Customize the system->Entity>Feature->Fields, you can find the lookup field to click it, then will show this page.but this is not important, this is just let you ensure related entity name, which is related to feature entity.
Business Applications communities