Functions in Microsoft Dataverse
A few days ago Microsoft announced the creation and use of function in Microsoft Dataverse (currently in preview). Functions use Power Fx to execute a set of commands within Dataverse that run on the server-side.
A few days ago Microsoft announced the creation and use of function in Microsoft Dataverse (currently in preview). Functions use Power Fx to execute a set of commands within Dataverse that run on the server-side.
This has been a feature that has been requested for as long as I can remember using Microsoft Dynamics CRM and the Power Platform, and finally it is here.
A few weeks ago Microsoft announced the availability of SQL Server Environment variables which will be able to support your Power Apps deployments as part of an ALM Process
For IT pros that have worked with database modelling for much of their career, the latest feature available in the Maker Portal, Data Workspaces will be a great tool to start working with.
As part of the 2024 Power Platform Release Wave 1, Microsoft has released (currently in Public Preview) the ability to create secured fields and mask either all or parts of the field based on regular expressions. This would allow us to show parts of the secured fields (such as the last 4 digits of a social security number) on the form without having to deal with custom scripts and not having the ability to export the full data of those fields.
Although this feature might have been out for a couple of months (at least in preview), I recently noticed that the new Dataverse connector (non-legacy), has some new actions that can be performed against other environments, and not only the current environment as was previously named Common Data Services Connector (Current Environment).
While working on a recent project to replace a low code platform with the Power Platform, one of the requirements that we had was to replace some of the Excel export and import functionalities that the existing system had to be able to send large Excel files into various other systems to be analyzed and consumed.
The AAD Users virtual table that was added to Dataverse has been a lifesaver for a lot of applications, especially when using Power Apps licensing as they provide the full subset of Active Directory users. When using Power Apps licensing, not all users are automatically synched to the Users table, so that is a great addition.
the team members on a project I am on mentioned that they were trying to change the width of a field in our unmanaged environment, but were not able to do this. This to me seemed a little weird, so I decided to investigate.
Up until recently the email description field or the body of the email have been stored within the Microsoft Dataverse data store. This is going to be changing in the coming months where the email description field will be moved to an Azure Blob Storage