Custom calculated fields are added to entities to calculate and store the results of the calculation. These fields support logical functions and conditions. This video demonstrates editing a calculated field to add a condition, and describes pros and cons of calculated fields in the CDS for Apps.
- [Instructor] I want to add a condition to the calculation … 'cause we have a different follow up for it. … You didn't come for appointment. … I'm going to add field to this appointment in the field, … it's going to be called completed … for the service being completed. … And this is actually simple two options, … and the options are yes and no. … And I'm not going to make this required, … and the reason I'm and going to make it required … is that the time this this entity is used, … we won't necessarily know that someone didn't come in … for their appointment. … I'm going to open up the Advanced Options … and I'm just going to add some text. … Mark no if contact no-showed or canceled this appointment. … Just so you remember that you can do that if you wish. … So here's the new completed field. … Now I want to edit follow up, … but I have unsaved changes in my entity. … That's why this is still bold. … So I'm going to click Save Entity to save the vehicle entity … with the new field, completed, that I have just added. …
- Recall the URL for the PowerApps portal.
- Recognize the template used to create a three-screen mobile app from existing data.
- Name the default type of entity ownership.
- Determine the type of relationship between two entities.
- Identify the prefix for Microsoft Dynamics entities.
- Explain where PowerApps business rules run, even on canvas apps.
- Recognize an example of an artifact type of component.