I'm trying to find the composite key of an extended F&O entity named ExpEcoResReleasedProductVariants. There are 3 pieces to the screenshot below:
- (top-left) The source/parent of the entity extension is EcoResReleasedProductVariant and you can see the keys.
- (bottom-left) You can see the keys for the custom entity ExpEcoResReleasedProductVariants.
- (right-center) You can see that ExpEcoResReleasedProductVariants really does exist and contains records. I can query these records via browser GET using filter syntax, but I must have key syntax in order to do PATCH operations against the entity.
A PATCH operation against F&O odata is required to be structured like this:
/data/ExpEcoResReleasedProductVariants(ProductMasterNumber='243-1001',ProductConfigurationId='000377',ProductSizeId='',ProductColorId='',ProductStyleId='')
I have also tried the following permutations:
/data/ExpEcoResReleasedProductVariants(ProductMasterNumber='243-1001',ProductConfigurationId='000377',ProductSizeId='',ProductColorId='',ProductStyleId='',ItemNumber='243-1001')
/data/ExpEcoResReleasedProductVariants(ProductMasterNumber='243-1001',ProductConfigurationId='000377',ProductSizeId='',ProductColorId='',ProductStyleId='',ItemNumber='243-1001',ProductMasterNumber='243-1001')
I have tried various combinations and permutations of what you see above, but in all cases I get errors like this:
<Error>
<Message>No HTTP resource was found that matches the request URI 'https://***.sandbox.operations.dynamics.com/data/ExpEcoResReleasedProductVariants(ProductMasterNumber='243-1001',ProductConfigurationId='000377',ProductStyleId='',ProductSizeId='',ProductColorId='',ItemNumber='243-1001')'. No route data was found for this request.</Message>
</Error>
How can I find the correct composite key so I can structure the odata request correctly so I can perform a PATCH against it? Note: The URL structure above will perform a valid GET and show data like in the screenshot, when it is correct. As mentioned, the screenshot above displays good data from an odata GET only by using filter syntax, not by using "composite key" syntax. For example:
/data/ExpEcoResReleasedProductVariants?$filter=ProductMasterNumber eq '243-1001' and ProductConfigurationId eq '000377'
What the AOT shows for keys is apparently not correct, else it would work.
I have downloaded /data/$metadata and that gives me a ton of data, but the keys for ExpEcoResReleasedProductVariants are not listed. In most cases, entity keys are listed in that metadata dump, but this one isn't.
There must be some solid way to know how to construct an F&O odata query using composite key patch syntax with the correct key attributes. How can it be found?
Thanks in advance for any help.
