[Step by Step] Dynamics 365 – Microsoft Forms Pro Survey Solution
Microsoft Forms Pro is an enterprise survey capability powered by both Office 365 and Dynamics 365.
Forms Pro is built on Microsoft Forms, and it offers new capabilities that make capturing and analyzing customer and employee feedback simpler than ever.
‘Forms Pro’ will eventually replaces the existing Dynamics Voice of the Customer Survey
Steps to subscribe:
- Connect to https://formspro.microsoft.com
- Either subscribe for a free 30 days trail or alternately you can also use Dynamics 365 30 days trails credentials.
- Provide your Office 365 Email ID and click on ‘Submit’ to complete registration.
Create a new Survey:
Once you completed the subscription, from the FormsPro portal
- Click on ‘Create a new form’ to configure your survey.
- Click on ‘Theme’ to choose the Survey Theme. This is an optional step.
- Provide the Survey Details like Name and Description.
- Next, to add Survey questionnaire, click ‘Add Option’ to add the available control options
- I’ve chosen ‘Choice’ control for this simple survey.
- Fill the Questions and Choices.
- Click on ‘Preview’ to preview the survey in both Computer and Mobile.
Send The Survey:
After your survey is ready, send it to your respondents and collect their feedback. You can send your survey in the following ways:
- Email: Send the survey link by using the built-in email capability.
- Microsoft Flow: Configure a business trigger by using Microsoft Flow to send the email.
- Embed: Embed the survey in a webpage.
- Link: Copy a link to the survey that you created, and paste it into a shared area.
- QR code: Send a QR code for your survey.
Respond to Survey:
- To show how the Survey would render to recipients, I’ve used ‘Link’ option and copied the Survey URL in browser tab.
- It renders as follows.
- Choose your response and ‘Submit’.
Analyze Responses:
- Click on ‘Responses’ tab to analyse the responses.
Survey Settings:
Click on ‘…’ and ‘More Settings’ to configure Survey settings.
- To deactivate the Survey (i.e.,Stop collecting the responses) uncheck the ‘Accept Responses’ checkbox.
- Deactivated Survey would show up as follows to Recipient.
- You can set the Date range of the Survey.
Entities that get added:
Following entities get added with ‘Form Pro’ survey solution
- msfp_emailtemplate
- msfp_question
- msfp_questionresponse
- msfp_survey
- msfp_surveyinvite
- msfp_unsubscribedrecipient
Refer this article for more details.
🙂
[Fix] Rollup field error – Record currency is required to calculate rollup field of type currency
I have added a new Rollup field of type ‘Currency’ to my existing custom entity ‘Customer’, which ‘SUM’ up the currency field’s data from related entity ‘Loan’.
Post customization, when I open the existing Customer record, following error showed up on Rollup field.
Reason:
- This error would occur, only those records created before the new Rollup field added to the entity, since they will not contain valid data in the Currency (
TransactionCurrencyId) field. - To check the understanding, I added the OOB ‘Currency’ field to the form and as expected, it was blank.
Fix:
- By Setting ‘Currency’ field manually, fixed the issue.
- Alternately, If the existing data is trivial, delete them all as the records created after the addition of the Rollup field, should automatically have the currency field set, and the rollup field should thus work correctly.
Notes:
- Those who are wondering what is ‘Currency’ field, the first time a new currency field added to an entity, Dynamics creates total of 4 fields, as following:
- If you notice, in the above list, ‘Currency’ is OOB field that gets added by Dynamics, which is a lookup to ‘Currency’ entity.
🙂
ADX Portals – adx_webformsession.adx_currentwebformstep is null
I got following exception while navigating through my ‘Web Form’ steps in ADX Portal.
adx_webformsession.adx_currentwebformstep is null
Reason:
- I had redesigned a ‘Web Form’ by deleting couple of existing ‘Web Form’ steps.
- However the associated ‘Session’ records, of deleted ‘Web Form’ steps, were still exists in the system causing the specified issue.
Fix:
- Delete all orphan ‘Web Form Sessions’ records from the system.
- Query all the ‘Web Form Sessions’ records which does not contain a ‘Web Form’, using ‘Advanced Find’ as below.
- Delete all records.
- Clear Portal Cache
- Issue should go away.
🙂
Common Data Model (CDM) – Intro
The Common Data Model (CDM) is an open-source definition of standard entities and a metadata system that enable consistency of data across apps and business processes.
Today, the Common Data Model is used within Common Data Service (CDS), which supports Dynamics 365, PowerApps, and the data-preparation capabilities in Power BI dataflows to create schematized files in Azure Data Lake.
With CDS we define an entity which can be leveraged by Dynamics 365, PowerApps and Power BI.
Dynamics 365 Healthcare Accelerator is an example of CDM which built on FHIR-based data model.
Explore the Common Data Model (CDM) using the Visual Entity Navigator
- Click on ‘Load from Github’ button, which load all available Open Source CDMs.
- Once definitions loaded, click on an entity to explore its schema
Refer this article to know more about CDM.
🙂
Dynamics Portals – Web Templates – ‘$ is not defined’ Error
Other day, I was getting ‘$ is not defined’ script error during my ‘Web Template’ load.
From the error, its clear that jQuery file reference was missing in Web Template.
The Web Template has a HTML with Liquid Template and script using jQuery and was rendering with no issues an hour ago and there were no changes made to the Web Template content.
Reason and Fix:
- ‘Use Website Header and Footer’ field was unchecked in ‘Page Template’ which was causing the issue.
- jQuery file would be implicitly available to the ‘Web Template’ when ‘Use Website Header and Footer’ field is checked on ‘Page Template’.
- Save the Page Template
- Clear the portal Cache and issue should be fixed.
🙂
[Step by Step] Canvas App using on-premise SQL server as Data Source
In this post, lets see how to build a Canvas App with data from on-premise SQL Server.
Using Gateways ,data can be transferred quickly and securely between a canvas app and an on-premises data source, such as an on-premises SQL Server database or an on-premises SharePoint site.
Lets get started to configure a Gateway and read the on-premises SQL Data which acts as a Canvas App’s ‘Data Source’.
Prerequisites:
- SQL Server with a Database and a simple table.
- Dynamics 365 subscription. Subscribe to 30 days trail here.
Configure a ‘Gateway’ to on-premise SQL Server:
We need to install ‘On-Premises Data Gateway’ service on the machine with ‘SQL Server’.
- Connect to PowerApps maker portal using your Dynamics 365 credentials.
- Go to Data -> Gateways and click on ‘+New gateway’ button.
- You will be redirected to downloads page and click on ‘Download’ under ‘On-Premises Data Gateway’ section.
- Download and click on the ‘GatewayInstall’ application.
- Provide your Dynamics 365 email (i.e., User ID) and click ‘Sign in’ to connect to Power platform.
- Provide your desired gateway name,recovery key and click ‘Configure’
- You will end up with below success screen.
- We are done with Gateway configuration.
- If you go to the ‘Services’ on your machine, you should see ‘On-premises data gateway service’ up and running.
- Go back to PowerApps portal and refresh the ‘Gateways’ and you should see the configure gateway.
Create a Canvas App:
As we completed ‘Gateway’ configuration, the next step to create a Canvas app and connect to on-premises SQL server using the ‘Gateway’.
- Click on ‘+Create’ and choose ‘Canvas app from blank’
- Provide the ‘App name’ and click on ‘Create’
- Now we need to establish the connectivity between Canvas App and SQL Server.
- Click on ‘Connect to data’ and select ‘SQL Server’ from the list.
- Choose ‘Connect using on-premises data gateway’ option and provide the SQL server, Gateway details and click ‘Create’.
- Select the table (i.e.,Contact) and click ‘Connect’ which creates a new ‘Data source’.
- Now add a Gallery component and map the ‘Data source’.
Additional Details:
- To install the ‘Gateway’, machine should have minimum configuration mentioned here.
- Gateway installs as ‘On-premises data gateway service’ on the server. Make sure this service is running all the time.
- Along with service, a desktop application by name ‘On-premises data gateway’ gets installed. You can enable logging and manage settings using this application.
🙂
PowerApps Portal – Intro
Those who are familiar with ADX Portals which later acquired by Microsoft and came up with ‘Dynamics Portals’ SaaS offering, ‘PowerApps’ Portal is the next evolution.
- With PowerApps Portals, Microsoft merging the capabilities offered by Dynamics 365 Customer Engagement portals in to PowerApps Portals.
- PowerApps Portals provides the ability to build low-code, responsive websites which allow external users to interact with the data stored in the Common Data Service (CDS).
- PowerApps Portals will seamlessly integrate with Microsoft services like Power BI embed, Microsoft Flow, Microsoft SharePoint, Azure Blob Storage, Azure AD B2C, and Azure Application Insights to enhance your portal with rich content and provide a personalized experience to your customers.
- All the components of Dynamics CE portals (i.e., Entity Forms, Web Templates, Web Forms,etc…) will be continued to available in PowerApps Portals.
- PowerApps portal uses the same ‘Liquid Template’ scripting conventions of Dynamics CE Portals.
How to get started?
- General availability of PowerApps Portal will from July 2019.
- A new App type called “Portal” will be available directly from PowerApps.
- You can subscribe here to be informed about the Public Preview availability.
Whats the upgrade path for existing Dynamics 365 CE Portals?
- All the existing Dynamics 365 CE portals will auto upgrade to PowerApps portals in coming months.
🙂
Badges
