You’re offline. This is a read only version of the page.
467
I have been building canvas apps the past year and have become used to the flexibility of being able to set default values with a varieity of options provided. Within a model driven app that uses the CDS it's not clear to me what all the methods are or best practice.
For example, I have a lookup field within the CDS entity to a Dynamics Talent entity named worker. The lookup uses the employee's worker ID and I woudl like to set the default value to the currentl user running the form.
This worker entity has a variety of additional columns to help drive defaults such as employee email. Within a canvas app you could simply grab the current users email and match it with the employee email within the worker column to default the correct worker ID.
Within a model app I am using the Business rules to set the default value however these don't seem to use formulas or not able to select additional fields, seems to be more simplisitic.
Is it not possible to walk to other fields within the entity like we can in Canvas apps?
LookUp(Workers, 'Primary Email Address' = 'Created By'.'Primary Email', 'Worker Number')
I can create calculated column (Text) such as employee's email and populate using createdby.internalemailaddress however this does not seem possible on a lookup column.
So am I missing something here? Is there a way to default a lookup column with a dynamic value?
Hi @Dudditz ,
Do you want to filter values of a lookup field?
Firstly, canvas app and model-driven app has many differences.
Canvas apps have more flexibility. While model-driven apps could deal with complex business logic.
You could filter values of a lookup field by turning on "Only show records where".
When this is enabled, the records that display when users search for a record will have additional filtering applied. This helps provide more relevant searches when setting the value of the lookup.
Here's a doc anout it in details for your reference:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/special-field-properties-legacy
Best regards,
I am beginning to think much of this flexibility we have in canvas apps simply does not exist in model however using embedded canvas apps could be a solution.
After testing out the embedded apps it seems like these are designed more for displaying related data rather than capturing data upstream and interacting with on a new record. Guess this is not an option for my scenario either.
#1
stampcoin
17
#2
mmbr1606
15
Super User 2025 Season 1
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
