Usually, we use SYSTEM user to specify the plugin’s execution context for business requirements that needs elevation of privileges.
And also we can neither update it from the user interface nor it is recommended to update the SYSTEM user.
If we try to update the user through code, we’d get the below error message
Error updating Users – No modifications to the ‘SYSTEM’ or ‘INTEGRATION’ user are permitted. [See the Execution Plan tab for details of where this error occurred]
CrmServiceClient svc = new CrmServiceClient(ConnectionString);
if (svc.IsReady)
{
var reqUpdateUserSettings = new UpdateUserSettingsSystemUserRequest();
// GUID of the System User
reqUpdateUserSettings.UserId = new Guid("18392d47-9dc0-eb11-8235-00224808ff23");
// reference the usersettings Entity
reqUpdateUserSettings.Settings = new Entity("usersettings");
// update the negativecurrencyformatcode to appropriate integer value
reqUpdateUserSettings.Settings.Attributes["negativecurrencyformatcode"] = 5;
var response = (UpdateUserSettingsSystemUserResponse)
svc.Execute(reqUpdateUserSettings);
}
SQL –
update usersettings
set negativecurrencyformatcode = 5
where systemuserid = '18392d47-9dc0-eb11-8235-00224808ff23'
With the new release, the CDS/CRM connection manager adds a new Interactive Login option in the CDS/CRM Connection Manager for Authentication Type as OAuth.
Interactive login allows the user to log in using his account details (to establish the connection with CRM) without the need for registering the application in the Azure Active Directory.
This is supposed to be used only during design time.
Enter User Name and the CDS/CRM URL and click on Test Connection.
The login screen pops up, where we can enter the credentials and sign in.
We’d receive the Test connection succeeded message.
Now we are ready to use the CRM Connection.
Now when we will run the package from within the Visual Studio (SSDT), it will again ask for entering the credentials.
The other option is to use the OAuth Type Password along with default Client App ID and Redirect URL
This adds the Advanced Lookup option in the Lookup dialog.
Clicking on it opens the Advanced Lookup Grid
We can perform SEARCH within a selected View, CHANGE a view, can FILTER it the results further to show only records owned, ADD a new record, SORT the grid.
The best part is we can open/edit an existing record as well as add new ones without losing the existing context.
Opening an existing record from the result opens the record in the new pop-up window as shown below.
Similarly, the Add new option opens the Quick Create form.
In case of special data type like Party List or Regarding, we can select multiple records of different entities we are presented with.
Similar the option to Add new records list all the tables/entities applicable to that lookup.
Thus the new advanced lookup makes working with Lookup much simpler and effective and we should start adapting / using it.
Azure Synapse Link (earlier known as Export to Data Lake Service) provides seamless integration of DataVerse with Azure Synapse Analytics, thus making it easy for users to do ad-hoc analysis using the familiar T-SQL with Synapse Studio, build Power BI Reports using Azure Synapse Analytics Connector or use Azure Spark in Azure Synapse for analytics.
Click on Azure Synapse Link and check the Connect to your Azure Synapse Analytics workspace (preview) and specify the storage account created in the previous step
Here we have selected the Contact and System User table for export.
On clicking Save, we got this error couple of times, even though the account being used was Owner across the Azure resources. Trying save 3-4 times more, allowed the link to be created.
Click on Go to Azure Synapse Analytics workspace, opens the Azure Synapse Studio
Within Synapse Studio we can see our Dataverse Database and run query.
Similarly, we create a Power BI report with Azure Synapse Analytics (SQL DW) connector.
Copy the Serverless SQL endpoint of the Synapse workspace.
Nishant Rana's Weblog 