Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | All TechTalks
I have data coming from CosmosDB that needs to be pushed into CRM. I am using a LogicApp for this.
There are multiple IDs that have different attributes associated with them:For instance the 'ems_featurecategoryid'. Each has a different name that goes along with its unique ID. (This the raw data that is within CRM)
Here is the CRM interface and the lookup field (feature category) in which I wish to push the CosmosDB data into:
Here is the CosmosDB data that hold this FeatureCategory attribute:
There are over 3000 of these. How would I map the IDs that are within CRM (Figure A) with CosmosDB (Figure C), so that when a value input is provided to the Feature Category lookup in CRM, this is recognized according to the value in CosmosDB?
This is what I am thinking:
I provided the Logic App with one of the GUIDs from Figure A. I am not sure if this is the right thing to do. The value is pushed through, but how do I account for all of the other IDs?
Any help or suggestions are appreciated.
A few things. If your Cosmos DB's table for feature category only contains names instead of the guid, then couldn't you ensure the ems_name field in CRM for your feature category is called exactly the same as the name in your cosmos DB table? If then that is the case then you can use a list record step to retrieve the CRM ID of the feature category based on the name of the feature category, like below. Noting the entity is your feature category entity.
You can then set the variable to be the feature category ID and then use that ID in subsequent lookups.
Another better way is if you can create a extra field/column in your cosmos DB to hold and map the CRM feature category IDs to your DB name values so that you can use the CRM ID values directly.
If this answers your question please mark it as answered.
You have two options here to achieve your requirement -
Option - 1
Use List Records to fetch Record ID based on the value which is coming from cosmos DB. Add filter criteria ems_name equals Cosmos DB Value
Options - 2
Create custom single line of text field in CRM and from logic apps map this field with the value from Cosmos DB while pushing data to CRM. No need for List records.
Now , In CRM Create Pre-operation plugin on Create and update message to set the lookup field based on new custom single line of text field.
Plugin code will get the text field value, it will query the feature category entity and will set the lookup field.
Don't show newly created text field on the form.
If you are not familliar with plugins in CRM, ask any CRM developer from your project team member he/she will be able to do this very easily.
Business Applications communities