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.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
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 | Upcoming TechTalks | All TechTalks
I have created a custom entity called interactions, and then another called interactiondata. I then created a relationship between them where an interaction can have many interaction datas.
I can create an interaction entity using the WebAPI and that works as expected, but when I come to create an interactiondata with a relation to the interaction, it all blows up. I suspect I am getting the odata.bind name incorrect.
I was wondering if there is an easy way to identify what that name should be.
I tried this:
The easiest and straightforward way to generate your requests is to use the CRM Rest Builder tool. You can download the latest version of this solution here: https://github.com/jlattimer/CRMRESTBuilder/releases
I want to update the parent customer for an account:
The generated code:
Good luck !
This looks amazing! Thank you for this, I will give it a go now!
Don't hesitate to keep up to date if it worked for you.
Lookup field tk_interactionid should be a schema name, check that.
It seems like the package does not show the custom entities that I have created in the list of entities. Do you know if this is a limitation of the solution, or a configuration issue?
This felt promising, but I still get an error:
So I found this as the schema name, which I have changed in my postman request
However, I still get an error:
Could this be the lookup item itself which is incorrect?
Sorry Mehdi, I found the entities now, I was looking for their label and not their name, my mistake!
I cross my fingers for you
Any news ?
Yup, turns out I had an error in my relationships, so as soon as I resolved them, I was able to use the code generated from that package, and it made it much easier to work out what I had to do. It did the trick perfectly. Thank you so much for your help and prompt response :)
Good news !! I'm glad you were able to solve your issue :)
Business Applications communities