Flow Not Showing Dynamics Lookup Field

[tommyly]

A Dynamics field is not showing up in Microsoft Flow.

As a troubleshooting measure, I'm doing this on Microsoft Flow: I execute a Dynamics query (Case entity). Immediately thereafter, I execute a Select action: the input is my Dynamics query values; I map 'test' to various columns (e.g. [Created On]). It works fine. As I scroll down the list of Dynamic content, I do not see [Contact] (aka responsiblecontactid).

At first I thought it was because it was a lookup data-type, but the list of Dynamic content includes several OOB and custom lookup fields.

I then thought maybe it was some setting (e.g. field security), but field security is disabled and all the other settings are identical to every other field that otherwise shows up on Microsoft Flow.

I've tried mapping it directly to item()?['responsiblecontactid'] but that field is not recognized.

I've tried creating an HTML table with all the values of my Dynamics query, and every single field shows up... (drum roll) except for [Contacts].

I've even created a temporary field in Dynamics ("flowTest") and restarted reloaded Flow. That colum appeared in the Dynamic content list in Microsoft Flow. So I don't think it has anything to do with my connection

I've triple-checked because I thought I was going crazy--[Contacts] (aka responsiblecontactid) exists.

Any idea why a field would not show up? Thanks in advance.

[v-alzhan-msft · Accepted solution]

Hi @tommyly ,

Would you please create a new field in the list with the same value in the Dynamics Lookup Field to see if the copy field would show?

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Begie]

Hey Tommy,

have exactly the same problem with the same field.....i try to do a get record contacts with identifier responsibe contact....but the field is not shown.

I see your question as solved, but don't see to see the resolution.

If you had a resolution, could you share it with me?

Rgds

Benny

[HallieG]

I have the same issue, did you ever figure it out? 

[tommyly]

---

@HallieG wrote:

I have the same issue, did you ever figure it out? 

---

Yes. Per this Microsoft documentation (Nov 2016),  the responsiblecontactid is deprecated. I believe Microsoft has made it available indefinitely but they have been trying to wean people from the field by making it unavailable through connectors (e.g. PowerApps, PowerBI, PowerAutomate).

For some time, I had created a classic Dynamics 365 script to copy the responsiblecontactid to a custom field new_responsiblecontactcopy. This seemed to work for some time, but as we started transitioning to the Unified Interface (which you probably will have to do soon  if you haven't transitioned yet; the deadline is early-December), we started manually converting some of our classic-workflows to PowerAutomate. I found that the classic-script to copy the contact information (i.e. responsiblecontactid --> new_responsiblecontactcopy) had an intermittent timing issue (e.g. sometimes PowerAutomate would trigger before classic-workflow and see a null value). There are a lot of things I could do, like forcing my PowerAutomate flows to sleep for a few seconds, or creating some type of semaphore system to have one process wait for another.

In short, it became easier just to bulk update all the old responsiblecontactid to the new_responsiblecontactcopy field and trick the end-users into populating the new custom field.

I hope that helps.