After completing the deployment, you need to do some configurations in both the Azure portal and FinOps to get the Dealer portal fully functioning. Let us start with the Azure components.
For exchanging files between the portal and FinOps, the Annata Dealer portal uses Azure storage accounts. You can use any storage account in your Azure subscription. For demonstration purposes, we will use the storage account we created while deploying the Annata365 Services (Azure Function Apps).
In the storage account, go to containers and create the following containers (name however you like):
Now go to Access keys on the left panel and copy the connection string.
In the back-end API configurations section, fill in the Azure storage account connections string and container names in the respective properties. The rest of the properties will have their default values from deployment.
We provide two options to send out user invites via email
To configure the portal to use Sendgrid set the Email client configuration to SendGrid and fill up the below configurations after you have set up the SendGrid account. (See details in a later section.)
To use Office SMTP set the Email client configuration to OfficeSMTP and fill up the below configurations
In the front-end app configurations, you can choose your logo, the background image for the login page, and the color theme for your portal. Provide a weblink for the logo and background image.
You can also set your company address using the below configurations available. This information will be shown inside the Contact Us infobox on the login screen.
Now let us move on to the F&O configurations.
The Document Queue framework is used to integrate external systems with Dynamics 365 for Finance and Operations and is designed to separate documents from the transport layer (technology used to deliver or receive documents). It provides a way to keep track of integrations, process messages on schedule, edit and reprocess messages on error, etc. The framework supports various communication types such as HTTP GET/POST services, Azure Queue, FTP, and emails. It also supports synchronous and asynchronous communications. The business logic that either creates outbound or processes inbound documents is specific for each scenario and can easily be developed and added to the framework.
To navigate to document queue in Dynamics 365 for Finance and Operations:
Organization administration > Document queue > Document queues
Document components decide how to handle the messages. There are three types of components:
There is a list of available components that can be activated as suitable.
To activate the appropriate Document components, go to:
Organization administration > Document queue > Setup > Document components
The event actions are used to generate or parse documents depending on the direction of the integration. An outbound event action can be triggered by, for example, business events, application events, user interactions, or custom codes. Inbound event action is triggered by the Document Queue when an inbound message is processed. Event action is specific for each integration based on what information the messages should include.
For Dealer Portal, select the document event actions below:
Channel adapters handle the transport of documents. Custom adapters that can be developed and added to the framework but included in the Annata 365 solution are:
For Dealer Portal, select the following channel adapters:
Set up the document group. This is created and configured at:
Organization administration > Document queue > Setup > Document groups
The Document action types link together document components. For each type of message (integration scenario), there must be a document action type. It defines what components are used, the direction of messages, and other properties that are used while processing a message. The types are created and configured at:Organization administration > Document queue > Setup > Document action types
For Dealer Portal, create a new document action type for each process with the 'Direction' set to ‘Inbound’ and the Active toggle turned on.
|Document action type||Event action||Channel adapter||Viewer|
|Case create (CC)||Create case||Case creation document adapter||Integrated viewer|
|Delivery report create (DRC)||Create delivery report||Delivery report creation document adapter||Integrated viewer|
|Device order create (DOC)||Create device order||Device order creation document adapter||Integrated viewer|
|Parts order create (POC)||Create parts order||Parts order creation document adapter||Integrated viewer|
|Parts return order create (PROC)||Create parts return order||Parts return order creation document adapter||Integrated viewer|
|Warranty claim create (WCC)||Create warranty claim||Warranty claim creation document adapter||Integrated viewer|
On the Classes fasttab of the document action type, you can edit the event action and define specific properties for the event action. The Device order created has such properties for the default sales pool for the device order created.
Some event actions can have specific properties which you can see by selecting the ‘Edit’ button beside the selected event action. The Device order created has such properties for the default sales pool for the device order created.
The Azure settings storage is a place to set up an external storage account to use for exchanging documents between Dealer Portal and Annata D365.
Set up a storage account by providing the storage account name and access key. You can get the storage account and access key setup earlier in this document. The access key will be encrypted upon saving. To set up the storage account, go to:
System Administration > Setup > Azure storage settings > Storage accounts
Note: The storage account must be in the same tenant.
Create blob containers for each document type in the storage account and set it up in Annata D365 by providing the container name and selecting the storage account via the drop-down.
To set up blob containers, go to:
System Administration > Setup > Azure storage settings > Blob containers
Create one record for each container created in the storage account
Once the Azure storage settings are configured, the blob containers are assigned to each document type in the Dealer portal parameters form.
To assign a Blob container to a document type, go to:
Organization administration > Organizations > Dealer setup > Parameters
The Annata Dealer Portal uses the BYOD feature available within the application.
To configure the BYOD database:
Data Management > Configure entity export to database
Provide the connection string of the portal database or the BYOD database connection string if you decide to have it separately, then select 'Validate'. Turn off the ‘Create clustered column store indexes’ toggle.
Refresh the entity store by going to:
Data Management > Framework parameters > Entity settings Select the 'Refresh entity list' button.
Once the validation is successful, click Publish. Select the entities below and click Publish again
Dealer portal product catalog hierarchy
Dealer portal product catalog items
Dealer portal product catalog tree
Dealer portal sales pool
Dealer sales pool parameter V2
Dealer portal delivery mode
Dealer portal return order line
Dealer portal sales orders
Dealer portal sales order lines
Dealer portal invoice headers
Dealer portal invoice lines
Dealer portal warranty claim header
Dealer portal warranty claim line
Dealer portal transfer order header
Dealer portal transfer order line
Device usage groups
Dealer device brand
Dealer device class
Dealer portal failure code
Dealer portal warranty term
Return reason codes
Dealer portal service campaign
Warranty claim groups
Warranty claim resolution codes
Warranty claim response codes
Warranty claim symptom codes
Dealer portal warranty claim misc. code
Dealer portal claim type
Warranty claim cause codes
Dealer portal city
Dealer portal country region
Dealer portal county
Dealer portal state
Dealer portal zip code
Dealer portal district
Dealer portal address format
If any data entity is updated, it will be mentioned in the release notes in the partner portal. Then you have to refresh that entity. To refresh
Remove that entity from all data management jobs
Find it from the Data entities tab and delete it
Go to Framework parameters and refresh the data entities
Publish the entity again
Add back to the data management job
Turn on change tracking for the entities that are in the transactional group. This will allow you to sync data to the portal incrementally. Select the entity and select ‘Change tracking’, followed by ‘Enable primary table’.
For Parts and Dealer portal case entity, select 'Change tracking', followed by ‘Enable entire entity’. Optionally, you can turn on change tracking for all the entities that are published.
Create export jobs for all the entities. You can follow the grouping as shown in the previous sections. When adding entities, use the same ‘Target data format’ as what you configured in the first step.
For the transactional data group, you should choose the 'Default refresh type’ as ‘Incremental push only’.
Note: If you have enabled change tracking for all the entities, then use the same refresh type. If you have not configured, use the ‘Full push only’ option.
Once the export job is set up, select ‘Create recurring data job’. Provide a name, batch group, and Application ID.
Tip: You can use the Application ID used to register the Annata D365 on Azure. To do so, go to System administration > Setup > Azure Active Directory applications.
Click 'Set processing recurrence' to schedule a batch job which will run at the specified intervals It is recommended that for the transactional data group, the recurrence time should be set to 5 minutes. For other export groups, it can be set up for hourly or daily based on how frequently the data is changed.
Optionally you can assign the new “Dealer portal” role to the user account that is used to register the app service. If you do that then you must add that role in the case category type security for each category want to use in the portal. Navigate to:
Organization administration > Setup > Cases > Case category type security
Follow the instructions below to sign-up for a SendGrid account using Azure portal. Then generate an API-key for your application.
Sign up for SendGrid Account
Sign in to the Azure portal.
In the Azure portal menu or the home page, select Create a resource.
Search for and select SendGrid.
Complete the signup form and select Create.
Enter a Name to identify your SendGrid service in your Azure settings. Names must be between 1 and 100 characters in length and contain only alphanumeric characters, dashes, dots, and underscores. The name must be unique in your list of subscribed Azure Store Items.
Enter and confirm your Password.
Choose your Subscription.
Create a new Resource group or use an existing one.
In the Pricing tier section select the free SendGrid plan.
Enter your Contact Information.
Review and accept the Legal terms.
After confirming your purchase, you will see a Deployment Succeeded pop-up and you will see your account listed.
After you have completed your purchase and clicked the Manage button to initiate the email verification process, you will receive an email from SendGrid asking you to verify your account. If you do not receive this email, or have problems verifying your account, please see FAQ.
Note: You can only send up to 100 emails/day until you have verified your account.
To modify your subscription plan or see the SendGrid contact settings, click the name of your SendGrid service to open the SendGrid Marketplace dashboard.
In your SendGrid dashboard, select Settings and then API Keys in the menu on the left.
Click the Create API Key.
At a minimum, provide the Name of this key and provide full access to Mail Send and select Save.
Your API will be displayed at this point one time. Please be sure to store it safely.