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.
 

Storage account and blob containers

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):

  • deviceimages
  • salesinvoices
  • packingslips
  • returnorder-attachments
  • claim-attachments
  • claim-invoices
  • claim-statements

Now go to Access keys on the left panel and copy the connection string. 
 

App Services configuration

Backend-API

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.

Backend-worker

We provide two options to send out user invites via email

  • Sendgrid
  • Office SMTP

SendGrid

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.)


 

OfficeSMTP

To use Office SMTP set the Email client configuration to OfficeSMTP and fill up the below configurations


 

Front-end

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.

Document queue

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

Document components decide how to handle the messages. There are three types of components:

  • Event actions
  • Channel adapters
  • Viewers

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

Event actions

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:

  • Create case
  • Create delivery report
  • Create device order
  • Create parts order
  • Create parts return order
  • Create warranty claim

Channel adapters

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:

  • Email and email notification
  • HTTP Post
  • HTTP Get
  • FTP
  • Azure Queue

For Dealer Portal, select the following channel adapters:

  • Case creation document adapter
  • Delivery report creation document adapter
  • Device order creation document adapter
  • Parts order creation document adapter
  • Parts return order creation document adapter
  • Warranty claim creation document adapter

Viewers

Viewers allow viewing of documents from the Document Queue page. We can use the ‘Integrated’ viewer for the Dealer portal.


Document groups 

Set up the document group. This is created and configured at:

  Organization administration > Document queue > Setup > Document groups

Document action types

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. 

Specific properties

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.

Azure storage settings

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.

Storage account

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.

Blob containers

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

Dealer portal parameters

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




A sales origin field is provided in the Dealer portal parameters form. This field is important as the sales origin for both parts and device sales orders are are defaulted from this field. By setting a value like ‘web’ or ‘portal’, it will make it easier to determine that the order was created from portal.



BYOD

The Annata Dealer Portal uses the BYOD feature available within the application.

Configure entity export database

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 entity store

Refresh the entity store by going to:
 Data Management > Framework parameters > Entity settings Select the 'Refresh entity list' button.




Publish data entities for export

Once the validation is successful, click Publish. Select the entities below and click Publish again

Dealer setup:

  • 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

  • Dealers

  • Members

  • Dealer member

  • Financing Customers
  • Dealer portal site
  • Dealer portal warehouse
  • Dealer portal parameters

Transactional data

  • Dealer portal packing slip
  • Dealer portal return order header
  • 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

  • Dealer portal delivery report header
  • Dealer portal devices
  • Dealer portal case
  • Supplier items
  • Parts

Device Setup

  • Device brands

  • Device classes

  • Device models

  • Device exteriors

  • Device interiors

  • Device usage groups

  • Dealer device brand

  • Dealer device class

  • Dealer device model
  • Life cycle setup
  • Dealer portal device order status approved transfer order
  • Dealer portal device order status in consignment list
  • Dealer portal device order status ordered not approved
  • Dealer portal device order status requested transfer order
  • Dealer portal device order status reserved for  customer

Warranty Setup

  • Dealer portal failure code

  • Dealer portal warranty term

  • Operation codes

  • 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

Address Setup

  • 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

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.

Export jobs

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.

Security

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

SendGrid

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

  1. Sign in to the Azure portal.

  2. In the Azure portal menu or the home page, select Create a resource.

  3. Search for and select SendGrid.

  4. Complete the signup form and select Create.

  5. 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.

  6. Enter and confirm your Password.

  7. Choose your Subscription.

  8. Create a new Resource group or use an existing one.

  9. In the Pricing tier section select the free SendGrid plan.

  10. Enter your Contact Information.

  11. Review and accept the Legal terms.

  12. 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.

Find SendGrid API key

  1. Click Manage.

  2. In your SendGrid dashboard, select Settings and then API Keys in the menu on the left.

  3. Click the Create API Key.

  4. At a minimum, provide the Name of this key and provide full access to Mail Send and select Save.

  5. Your API will be displayed at this point one time. Please be sure to store it safely.