i am connecting to the new CDS 2.0 using the new CDS connector (preview), and noticed that when i use the collect or ClearCollect functions, it skips the lookup fields in the collected table (it doesn't even get the ids of the lookup fields).
this behavior was not in the old CDS 1.0 premium connector!
Could you please share more details about the entity you used here?
Is it a custom Entity, or a system one?
The lookup field under the New CDS seems to be a little different from the old one.
It seems the field is mostly build on top of the entity structure from Dynamics 365, which only keeps the PrimaryKey of the parent entity.
You may check more details from the following document:
it is a custom entity, and i tried to connect to the same entity using the two different connectors available now (Dynamics 365 connector, and the CDS preview connector)
when i use the dynamics connector and use the ClearCollect function, it will retrieve all columns including the primary keys of the parent entity/ies.
while if i use the CDS preview connector and use the same function ClearCollect on the same entity, it will retrieve everything EXCEPT the lookup field, i.e. it is dropped!
Has this issue been resolved? I'm using the default CDS connector to connect to custom entities in my environment and when I use ClearCollect to pull in the data, any lookup value or Option set value remains blank in my collection.
Check out new user group experience and if you are a leader please create your group
Next call is happening on April 21st at 8a PST.
May the fourth be with you, join us online!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.