A common scenario when creating a powerapp is using a header and a lines table. We are all used to working with this in Finance and Operations. Common examples are Sales order header/Sales order lines and PO Header / PO Lines. In this video we will take a look at how we can take advantage of relations between table to build our apps faster.
Choice fields are commonly used in database tables to limit what data can be put into a field. It's important to know how to filter with them.
Before you start to create an app there is an important step that you should consider taking because inevitably at some point you will want to move your application to another environment. Either a Dev to Test move or a Test to Production move.
In this video we take a look at how we can satisfy simple reporting requirements in Dynamics 365 Finance and Operations with Power Automate.
In today's video we take a look at the patch function in powerapps to help us add a record in Dynamics 365 Finance and Operations.
If you have been working with Dynamics 365 for very long you have probably at some point or another have had to default a field or fields on a form. Normally what you have to do is work with a developer to add the defaulting logic to the form.
The ability to trigger alerts exists on almost any record type in Dynamics 365 Finance and Operations. Previously you could alert someone by sending an email.
The setup for virtual entities has you bouncing around a little bit but is straight forward. Hopefully, you found this blog post helpful.
In this week's video we take a look at how to add a bing map to our power app.
Today's video is pretty fun we're going to take some documents, AI Builder and Power Automate to create an entry in a common data service entity.