Timeline for Create annotation to a contact entity in Microsoft Dynamics CRM by API
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2022 at 15:48 | comment | added | Anderson Luiz Ferrari | I had to use the field "Schema name" which is CASE SENTIVE! | |
| Apr 4, 2020 at 14:01 | comment | added | Mr Moose | In addition to all of that, I found that the case of the attributes is important too. For example, I had "[email protected]" (which failed) vs "[email protected]" (which is how it is reflected in the CRM GUI..and this worked). | |
| Apr 30, 2019 at 23:38 | comment | added | Nathan |
Indeed the property logical name and the navigation property name are not consistent so checking the docs is essential. Additionally I had to drop the leading slash in the value so to specify a value for "businessunitid" I had to use: "[email protected]": "businessunits(b6c0d6c6-a07f-e611-80e8-c4346bc49e60)".
|
|
| Feb 16, 2016 at 19:53 | comment | added | Justin | I believe that it is because this is specific to the regarding field on notes, which can lookup to various entities. Therefore, the _contact is dependent on which entity you wish to set it regarding (always objectid_entityname for notes regarding field). | |
| Feb 16, 2016 at 16:28 | comment | added | zabby | This is better than the accepted response since it only uses 1 call. I'm guessing the addition of "_contact" (or something similar) depends on if the current record is a parent or child. | |
| Jan 5, 2016 at 18:33 | history | edited | Nathaniel Ford | CC BY-SA 3.0 |
deleted 25 characters in body
|
| Jan 5, 2016 at 18:28 | review | Late answers | |||
| Jan 5, 2016 at 18:33 | |||||
| Jan 5, 2016 at 18:06 | history | answered | Justin | CC BY-SA 3.0 |