You are currently browsing the category archive for the ‘Configuration’ category.

This one is just a quick tip.

We’re all used to the classical interface, as we’ve been configuring and testing in it since the beginning. Which is why some small things could make us pause for a moment to think.

Working with Apps now is the new trick, and takes a bit of mind-bending sometimes. It’s like teaching an old dog new tricks. Read the rest of this entry »

Another one on the best practice / bad practice topic. Working with custom security roles this time.

We have an option to start configuring a new Security Roles from an existing role. You might be tempted to do that, thinking it’ll save you time and minimize the potential for missing something. But, there’s a problem with that approach. In order to create a new role, you should be spending pretty much the same amount of time to create one from scratch versus a Save Create New (Yes, that’s what it’s called, would have been better named Save As for consistency). Read the rest of this entry »

An observation more than anything, but I’m seeing this happening every now and then, and it’s worth putting it out there.

With great power comes great responsibility.

The platform allows us to create new forms by simply opening an existing form and selecting Save As. We tend to use that, as it’s easy to start from an existing form, and make small changes when creating new forms. But, as easy as that is, it has the potential to create a big problem.

Read the rest of this entry »

Nowadays the toolbox is getting big and heavy. We have some level of overlap between some of the various platforms joined under the Dynamics 365 name, we leverage various features of Office 365, we integrate with other products like SharePoint and OneDrive. And this is just scratching the surface. I mean, really, look at the “new fave kid on the block”, the Power Platform.

And here’s another one for the non-developer: Microsoft Forms Pro. It’s now in public preview.


Read the rest of this entry »

Continuing with the Asset Management example from THIS previous post, I had a requirement to be able to create a view showing all assets that do not have a document library location created on SharePoint. Usually, for an asset, at the minimum, a specifications sheet must be attached, including the installation notes.

This is a very simplistic approach, using a Two Options field type, set to default Yes/No to use for filtering, and a workflow to update this field when documents are added.

So, first step, add the field to the entity. I will name it Documentation (asm_documentation), and set it default to No. You don’t necessarily have to add it to any form, as it’s not relevant on the asset property.

Next, create a view based on the Active Assets default view. I named it “Active Assets with no Documentation”. Add a column to the view showing the Documentation field we just added, as well as other fields that make sense. Add a filter to only show records with the Documentation value of No.


Next, the workflow we create will update the value of the Documentation field to Yes if documents are attached to the record. We do this by running the workflow against the Document Location entity. Set it as a background workflow. Set the conditions as described in the screenshot below.


Save and Activate the workflow. Publish all customizations.

Now start loading some assets into your asset management. Add documents to some, and leave others with no documents attached. Once done, navigate to the “Active Assets with no Documentation” view. You will see a listing of assets that are missing the documentation library on SharePoint. You can then add the necessary documentation, assign the records to the proper team for documentation management or trigger a process to request the installation team to load the required documentation.


And with that, you can determine which records do not even have a related SharePoint document library created.

NOTE: Once you navigate to Documents on the respective record, the folder is created on SharePoint and triggers the process to update the Documentation field value to Yes. This does NOT determine if any documents are actually loaded in the respective SharePoint folder. We’ll tackle a process to determine if various types of documents are attached to a record in another post.


MVP Reconnect

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 617 other followers

Follow Dynamics 365 Wizardry on