Unanswered

How to update a Lookup field in CRM using LogicApp Flow

(0) Share

Report

Posted on by jasmine2020 Microsoft Employee

I have created a LogicApp to pull data from CosmosDB and send to CRM. All of my fields cross over except the "lookup" fields.

For example, Feature Category, is a Lookup field within CRM.

Any field that looks like this with the magnifying glass:

My question, is how would I implement this in the Logic App?

Just doing this does not work, even when I add quotes.

The Feature Category that I pulled from CosmosDB already has a value:

My dilemma is:

How can I get this 'lookup' field to accept my value within the LogicApp?

I tried doing this and it does not work:

Any help or suggestions are appreciated.

Categories:

Building flows

I have the same question (0)

All responses (22)

Answers (2)

Verified answer

Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Hello @jasmine2020

You need to do a list records on the entity that the lookup is from.

Doing the list records will get you the Primary Id.

This ID can be identified by the guid.

For example if my entity is Accounts. The field I will need to grab from the list records will be called Account.

this guid is what needs to be passed into the lookup.

Was this reply helpful? Yes No
jasmine2020 Microsoft Employee on at

Like (0)

Report

Hi,

I see the ListRecords option here, but I am still unsure of exactly how this works.

So I am wanting to autopopulate the fields within CRM with the data that I have in CosmosDB:

But because its a 'lookup' I keep getting an error. How would I use List Records to solve this, when it doesnt contain the
'Feature Category' field that I need?

I am new and am just trying to understand. Please add insight if you can. Thank you

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Hi @jasmine2020

Okay no problem. The first thing we need to do is understand the entities that are being used.

We need to check what the data types are inside the Features entity.

could you run the flow with the list records action on the features entity, like in your picture.

you could use the top count option and put 2 so only 2 records will get returned.

if you could please paste the output of the list records. This will help me better understand your data model so I can better assist you

Was this reply helpful? Yes No
jasmine2020 Microsoft Employee on at

Like (0)

Report

Sure thank you. Here is my full logic app:

Is this what you need?

Was this reply helpful? Yes No
jasmine2020 Microsoft Employee on at

Like (0)

Report

Oh I think I misunderstood.

Do I need to actually 'Run' this?

and then view the output??

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Hi @jasmine2020

Thank you for sharing.

Kind of, I actually need to see the data inside your feature entity

Could you add a list records under your http trigger.

Select your Features entity and, run the Logic app.

Please share a sample of the output from the list records action.

Was this reply helpful? Yes No
jasmine2020 Microsoft Employee on at

Like (0)

Report

Here are some of the outputs after I ran this:

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

Thanks @jasmine2020

This helps a ton!

Does the feature entity contain any real data yet? Or are you basically transferring all cosmosDB to CDS?

Was this reply helpful? Yes No
jasmine2020 Microsoft Employee on at

Like (0)

Report

No thank you!

No it doesn't really have the data in it yet, I am just trying to see how I can push the data from cosmosDB into this 'lookup' field.
I had to add that parameter:

feature category

The feature category looks like this in CRM:
Since its a 'lookup', this is whats confusing me....

Was this reply helpful? Yes No
Jcook 7,781 Most Valuable Professional on at

Like (1)

Report

@jasmine2020

So a lookup is just another table, that can relate to one or more other tables. And the way they relate is by using the PrimaryID / guid.

Okay so, since features has no data. You will have to create the lookup before you can use it.

Could you check and see if the features entity has a name field?

Was this reply helpful? Yes No