Hi there! I'm working on building my first power app from D365 data. I had tons of issues getting the forms to save using the actual D365 connection, so I'm using the CDS variants of the entities I need.
The app is built on a custom Application entity, and ever since I changed to the CDS connections I've lost scope for all my lookups in my browse view. I'm hoping for some information on how to get access to them, and any more information on how things are handled behind the scenes would be great too.
Customer is a Contact, Product and Shipping Speed are Products, and Destination Address is a Custom Address entity. There are all brought in as CDS sources.
You can see in the default browse screen all 4 Lookups are missing from available fields to select from Application, though they should exist as fields in every app. The Lookup function up top worked when I connected the data via 365, but not with the CDS.
The lookup fields ARE available to add on the edit screen. I'm just not sure what the difference is and why they aren't available/out of scope on the browse screen.
I'm trying to understand a bit about and configuration and seeing what data is stored where so I can troubleshoot why I'm running into lots of things like this! I know most of this can be worked around by scripting in the variables and stuff, but I wanted to work with the default template before I dive in that!
Thanks so much,
Solved! Go to Solution.
Hey thanks for your response! I do have correct syntax for obtaining a lookup in the box as per Photo 2, but the underlying issue is that This.Customer, as well as the rest of the lookup fields, are not being recognize/accessible as part of the gallery screen for some reason. This prevents the look up function such as LookUp(Contacts, contactid = ThisItem.Customer).'Full Name' from returning a result because ThisItem.Customer is not accessible.
Here is a picture of what my formula/errors/hints looks like for the field in question:
Thanks so much again,
Ah this was it! I've used the previous formula before to compare Id and Customer since if you add only This.Customer to a form it returns the GUID but this is probably better practice anyway!
Thanks so much, Kudos!
FIll out a quick form to claim your community user group member badge today!
The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Apps Community!