Skip to main content

Introducing the new WYSIWYG model-driven form designer

Image
By
Microsoft recently announce their new WYSIWYG model-driven form designer.  See here for more details.

Initially looking at this, this designer seems pretty amazing and will resolve a lot of the pain points identified with using the classic Dynamics 365 form designer, such as:

  • Allowing makers to see how the form would look to end users as they configure
  • Enhanced fields pane with searching and filtering capabilities on the left
  • An always available properties pane allowing makers to configure components of the form without having pop-ups appear
  • A tree view to quickly navigate forms fields and controls
  • The ability to switch between form factors / sizes to see how the form will look on different devices
  • Save and publish via a single button


To use the new form designer, you must click on either Edit form (preview) or Add Form -> Main form (preview) from PowerApps.

Note that this is currently out only in public preview, and therefore consider this a very early version of something exciting to come.  I was able to play around with it a bit, and ran into a few challenges.


First off, the designer seemed a bit sluggish (slower to load and navigate around the UI elements). Also, I wasn't able to drag / drop a field onto the form, which you can with the classic designer. I had to click on the form where I wanted to add my elements first, then click the field, or tab, or section I wanted to add.  Additionally, I couldn't see how to add things such as sub-grids, spacers, quick view forms, IFRAME's, web resources, etc.

I'm sure as this feature matures, Microsoft will work on making it more reliable.  Regardless, it's pretty awesome to see where the public preview currently is with allowing makers the ability to change properties directly within a sticky pane without drowning in a sea of pop-ups.

Comments

Post a Comment

Popular posts from this blog

Announcing the New Dynamics 365 Toolbot Chrome Extension!

By
Today I am excited to announce the new Dynamics 365 Toolbot! This new Chrome Extension will allow you to perform commands that will help you with your development or administrative tasks. The extension can be found here - https://chrome.google.com/webstore/detail/dynamics-365-toolbot/kljiiminicfmdlplhejocopfmgmipach.

Note: Currently, due to the APIs being used, it only works on v9+.

First, navigate to the link above using Chrome and install the extension. Then, head to your Dynamics 365 environment and open a record. From there, click the little blue robot icon in the toolbar of Chrome which will pop open the Toolbot.



Click the text box and a list of commands will display. You can select or type any of the commands and hit Submit to execute them. Some commands require you to replace the default token with the desired request.


For example, select or type "display id" and click Submit and the Toolbot will display the current record's ID.



The majority of the commands should …
Post a Comment
Read more

Dynamics 365 ToolBot: Auto-populate the form

By
Today I released a new command for the Dynamics 365 ToolBot that I am really excited about! If you're not sure what the Dynamics 365 ToolBot is, it is a new Chrome extension that I released recently that allows you to quickly execute helpful commands for administrators, developers and testers.

This new command, called "Fill Form", will automatically populate all the fields on the form with random data. As a developer, I always need test data and I am the worst at coming up with fake data to use. With this command, you can navigate to any record, open the ToolBot, type "Fill Form" and your record will instantly be populated with random data so you can quickly save the record and proceed with your testing.


A few things to note about this command:
It attempts to detect contact fields (based on the field name) such as first name, last name, email, phone and address and populate those fields with realistic fake dataAny other field will generate random data based on t…
Post a Comment
Read more

CRM 2011 LINQ - All Columns vs. Selected Columns

By
When creating LINQ queries in CRM 2011, it is easy enough to return the whole column set of the entity record without even thinking about the impact.  
Below is an example of querying all contacts from Chicago and returning all columns for each contact record.


This can be a big performance impact depending on the amount of columns that exist on the Contact entity and how many contact records exist in the system.  Another issue is that it could cause errors down the line if some of the attribute types are changed in the CRM system since the data is being bound to a model class that could be out-of-sync.
From the MSDN article on constructing LINQ queries (http://msdn.microsoft.com/en-us/library/gg328328.aspx), we can see that the select clause creates a column set:
The select clause defines the form of the data returned. The clause creates a column set based on the query expression results. You can also define an instance of a new object to work with. The newly created object using the…
5 comments
Read more