Skip to main content


Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign

Recent posts

Power Automate: Avoid Apply to Each for List rows action (DataVerse)

If you do not want to use the Apply to Each loop after a Dataverse List rows action you can use the following in a Dynamic Content / Expression box to directly use a field's value in e.g. Compose action: first(outputs('List_rows')?['body/value'])?['apx_fullpath'] instead of apx_fullpath you can use whatever field name you need for the entity that's been queried before.

Workaround for broken sort buttons on the record creation and update rule items grid

In the customer service admin center app, if you open a "Record Creation and Update Rule" and go to Step two with the RCU items grid and you have more than 10 items in the subgrid available you might face a sorting bug which is recognized by Microsoft. Once you go to page 2 or any higher number and try so change the sort order / sequence number the sorting is not working or doing anything at all.   Microsoft support has given me this temporary workaround until this bug is fixed: Open the RCU item and open the Level Up for D365 Chrome extension and hit the "RECORD ID" button to retrieve the GUIDs of the source and target items that you want to switch the order. In Chrome browser hit F12 and go to the console tab. There insert the folloing lines of JavaScript to change the sequence number of each item: var data = { "sequencenumber" : "12" }; Xrm.WebApi.updateRecord( "convertruleitem" , "GUID of previous position number&

How to quickly update an attibute from a browser bookmark

 As a developer or tester sometimes its really nice to have a direct way to update an attribute on the current record. To accomplish that you can simply bookmark a new page in e.g. Chrome and add this little piece of JavaScript into the URL field: javascript:(function(){const;const;const fldName = window.prompt("Please enter the attribute name");const fldValue = window.prompt("Please enter the attribute value");const jsdata={};jsdata[fldName]=fldValue;Xrm.WebApi.updateRecord(entName, curId.replace(/[{}]/g, ''), jsdata).then(function success(result) {window.alert('${entName} was successfully updated');},function (error){window.alert(error.message);});})() An alert box will ask you for the internal attribute name and a second for the value. This might not be the best way to do it but it will give you a clue on how to change it for your own needs. (This script will only work

How to create new (missing) columns for entities in your Data Export Service Azure SQL database

Usually the Data Export Service (DES) automatically picks up changes on entities and creates new fields/columns in the Azure SQL database that is connected to your DES profile. Our experience was that this automatism is not always reliable thus we had to come up with a workaround. Microsoft Support suggested us to create missing columns on the export database ourselves manually, which I did. As there is currently no other official documentation on this topic I thought I should share this article with the rest of our awesome community. 1. Completely recreate the entity table The 1st approach to solve this issue would be to go inside your DES profile and deselect the target entity from the list of entities to sync and save the changes. Next delete the target entities tables and user defined table types with the script provided here:

How to add your personal PowerBI Dashboard as a system dashboard

New Approach: Attention: Microsoft added this feature out of the box, so that the manual approach below is not required anymore. More to this can be found here: Old Approach: The general guideline on how to create a personal dashboard is described in this article: But what if you want to rollout a global PowerBI dashboard for all users? With some tweaks you can manage it to make it work… 1. After you have created your personal dashboard you need to extract the formxml of that dashboard with this URL query in a browser tab:$select=name,formxml&$filter=type eq 103 and name eq 'Ticket Status' Replace… type = 103 => PowerBi Dashboard name = 'Your PowerBI Dashboard Name' In the result copy the XML part out of the "formxm