What is the point of having a "Label" Dynamic Content option when it doesn't actually work?
For example, my Trigger uses the Dynamics 365 on Record Create/Update.
I have a field that we'll just call "Test Field" that is multi-select.
The labels for this field are:
But the actual values stored in the Entity are:
Those stored values mean absolutely nothing to me without the labels.
I go to add a Compose Action and type in "Test Field" for the Dynamic Content. This brings up two options:
"Test Field Label"
The second one should return the labels "Apples", "Oranges" instead of the stored values 799800000, 799800001, etc. Again, totally meaningless to me and very inefficient to get the actual Labels.
So I pick "Test Field Label" for the Compose Action, trigger the Flow, and it returns null despite the "Test Field" being populated. Using "Test Field" by itself, returns the array of values, so one would think "Test Field Label" would not return null.
So what is the point of having this as a Dynamic Content option when it doesn't actually work? Will Microsoft actually get it working at some point in time? I've been waiting for almost two years. Would be a huge time saver.
@ishraqiyun77 - I would suggest you move to the "Common Data Service (current environment)" connector. The "Dynamics 365" connector is deprecated. Also, the "CDS (ce)" connector can only be used when the flow is created from a solution.