My schema requires I use multi-element access between tables... (ie. Company+Employee) not an uncommon database problem. Power Apps allows you can create multi-field keys but does not allow you to use then in model-driven development.
I read that one method is to create a calculated field and concatenate the fields into that. but the CONCAT() function does not work with fields that are either LOOKUP or CHOICE.
Solved! Go to Solution.
This worked great in getting a calculated field that was a concatenation of two fields. Thank you!
Now I am attempting to use that field as a lookup in the child table. It works in a very odd way. In one instance it brings in the locally defined field (of the calculated column) in the parent table but on the looked-up field in the parent. In another case the parent table shows as a popup table but when a record is selected no data is copied into the child field. In another case where the parent calculated field is composed of two lookup fields no popup table shows at all.
I tried using the Calculate function when defining Dataverse table column for getting a value out of another column (lookup) in the same Dataverse table. It should work based on Microsoft note (https://docs.microsoft.com/en-us/power-apps/maker/data-platform/define-calculated-fields) by add a "." and the required column name from the source table. I was able to save the Calculate function without errors prompted. However, after adding a new record, such Calculated field shows blank results while other fields in the same table are correct. Anyone has any ideas on what might went wrong? Thanks
Keep up to date with current events and community announcements in the Power Apps community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!