Setup

incadea Automotive365 Network Management (Publisher) comes with the Role Center:

You can select the Role Center by clicking on Settings ➔ My Settings. For the field Role select the one mentioned above.

.

Fig. 9: My Settings - Role Center

.

Fig. 10: Role Center Selection - Available Roles

.

Fig. 11: Role Center - Data Distribution Admin

The rolecenter provides quick access to the pages described in the following chapters and gives an overview of the current active Subscriptions, Transmission activity to the subscribers and Maintenance.

In the Transmission section the following Cues are available:

Maintenance On displays the tables by filter groups and subscriber that are under maintenance so no related data can be downloaded from those subscribers.

When the subscriber belongs to another organization or a different environment on Azure, it is necessary to grant the consent in Business Central. To do so, click on Grant Consent on the newly created AAD Application Card.

.

Fig. 15: Grant Consent

The user which gives the consent needs to have one of the following roles:

Regarding these roles, please check the official Microsoft documentation:

Azure AD built in roles - Azure Active Directory

The Data Distribution Administration page is the centralized tool on the publisher to handle the setup of tables and their subscription to the specific subscribers. Moreover, the tool provides additional actions such as:

To open the Data Distribution Administration page, click on Administration on the Role Center.

.

Fig. 16: Open Administration on Role Center

.

Fig. 17: Data Distribution Administration Page

From the Data Distribution Administration the first step should be to setup which tables will be available for subscription. Click on Subscription Tables on the Data Distribution Administration page:

.

Fig. 18: Open Subscription Tables

The page Data Distribution Subscription Tables opens:

.

Fig. 19: Setup Data Distribution Subscription Tables

The records can be created one by one or by clicking on the Assist Edit of the Table No. field, which allows to select multiple tables to be created.

Each table can have different filter groups. By default, the system creates the “GENERAL” group. In normal conditions this single filter group should be sufficient. A description of the fields is provided below:

.

Field	Description
Table Group Code	This field allows to group tables with the same post-processing logic. It works along with the field Priority so that the tables are imported in the subscriber following the sorting by Table Group Code and Priority. Object Type (Post Processing) can be “Report” or “Codeunit”. In the example on the screenshot above the Codeunit 5069828 will be run on the subscriber once all tables from SETUP group are downloaded and processed. Therefore, the post processing object must exist on the subscriber.
Group Name	Name of the group related to the Table Group Code
Table No.	ID of the table. The Assist Edit allows to do a multi-selection of the tables to be created and not one by one.
Table Caption	Caption related to the Table No.
Subscription to Company	Normally will be empty. In case the table is Data per Company it is possible to setup a different company than the one shared with the subscriber if for some reason the data in the publisher for a specific table is not available in the main company.
No. of all Table Records	Calculated field with the current number of records.
Priority	Priority of the data import once it is processed in the subscriber. It works along with the field Table Group Code so that the tables are imported following the sorting by Table Group Code and Priority in ascending order so that a table with Priority 1 is imported prior to 2 and so on.
No. of Blocked Fields	Count of the fields which are blocked in such a way that they are not considered at all when the record is processed in the subscriber or only considered for the insert of the record.
Keep Locked After Modification	This field is used to keep a lock on the table while this table is being updated in the publisher, e.g. through a batch update of the table for several records or by manual changes on it. The possible options are as follows: 1 Min: This is the default value. When the subscriber connects to the publisher and asks for what's new, the publisher checks if the table is being updated during the last minute and so no data can be retrieved for this table or any of the tables that belong to the same group. 2 Min: Same, but with that time span. 3 Min: Same, but with that time span. 5 Min: Same, but with that time span. Never Lock: No lock is considered in the table.
Maintenance Mode	The Maintenance Mode can be set/unset manually by clicking on the Maintenance action.

Click on Fields to open the list of fields which are related to the selected table.

.

Fig. 20: Open Fields List

.

Fig. 21: Transmission Fields

As shown on the screenshot above, it is possible to setup the way the field is considered during the update of the data in the subscriber. Thus, there are three options to select on the Subscriber Update:

Once any field has any kind of block, either I- or --, it is displayed in the No. of Blocked Fields column:

.

Fig. 22: No of Blocked Fields

On the Filter Groups FastTab on the Data Distribution Subscription Tables page you can setup different sets of filters for a specific table. Normally is should be sufficient enough with the “GENERAL” group, which is created automatically whenever a table is inserted.

.

Fig. 23: Filter Groups - Setup Filter

It is possible to add new filters to the “GENERAL” group by clicking on Manage ➔ Filters or in the field No. of Filters in the Filter Group Line.

.

Fig. 24: Add Filters

This action opens the Edit - Filter Fields page. In the example below only the records with discount greater then 0 are transmitted.

.

Fig. 25: Filter Fields

It is possible to create new filter groups other then “GENERAL” to fulfill more complex scenarios but use this wisely to avoid sending repeating information in different groups.

As it can be seen in the Filter Group - Add Filters screenshot, by clicking on action Fields or on No. of Blocked Fields, it is also possible to set block filters on Filter Group level in the same way it has been shown on table level.

.

Fig. 26: Subscription Tables - Maintenance

.

Fig. 27: Filter Groups - Maintenance

The Maintenance action is available on the Subscription Tables at the top of the page and on the Filter Groups FastTab. This action sets the maintenance mode in the selected tables and filter groups so that no data is transmitted to the subscribers. There are some ways of selecting the records by clicking on the Maintenance action.

.

Fig. 28: Set Maintenance Mode

Once the Maintenance Mode is set, the user can see its possible value in the field Maintenance Mode of the table or filter group.

The possible values are as follows:

.

.Example of execution (after clicking on the Maintenance action at the top):

.

1.	. Set the values on which the Maintenance Mode should be executed. ⇒ . Fig. 29: Set Maintenance Mode - Example
2.	. Click on Yes on the notification. ⇒ . Fig. 30: Confirm Maintenance Mode ⇒ The tables on which the Maintenance Mode is activated are now shown in red. In the column Maintenance Mode the periode is shown.   . Fig. 31: Tables in Maintenance Mode

Note that when setting the maintenance mode on table level it is automatically copied to the filter groups of that table. As described before, it is still possible to set a different maintenance mode on filter group level if for some reason it is required. But normally it should be sufficient enough with the table level.

Once the setup of the tables has been done as described, it is possible to create some subscribers and subscribe to the tables and filter groups defined in the Subscription Tables page. This is done in the Data Distribution Administration page by clicking on the + new action:

.

Fig. 32: Add new Subscriber

.

Fig. 33: Subscriber Card

The detailed description of the fields is provided as follows:

Once the setup of the tables has been carried out in the Table Subscriptions page and a subscriber has been created, the system automatically copies all the available tables and filter groups from the Table Subscriptin page to the subscriber and they all appear as subscribed (bold) in the Data Distribution Administration page (same as in the Subscriber page seen on the screenshot for that page.

If some tables are not needed by the subscriber, it is possible to select them and use the Unsubscribe action as follows:

.

Fig. 34: Unsubscribe Tables on Data Distribution Admin page

.

1.	. On the Data Distribution Administration page, select a subscriber.
2.	. In the Tables section of that page select the table, you want to remove from the subscription and click on Unsubscribe. (Subscribed tables are shown in bold). ⇒ The line where you have unsubscibed is not displayed in bold any longer. This indicates, that the subscription has been removed successfully.   . Fig. 35: Removed Subscription

You can select more than one table by pressing [Ctrl] while clicking at the needed lines. A checkbox on the left side of the list appears, where you can see, which tables are selected.

.

Fig. 36: Select more than one table

The same procedure is applied to the Filter Groups part on that page in case their table is subscribed. If their table is not subscribed, no subscription action is allowed for the Filter Groups part.

Note that in the Data Distribution Administration it is not possible to modify the tables, filter groups, block fields, set a maintenance mode, etc. These changes must be carried out in the Subscription Tables page as explained in the chapters earlier. As a rule, it is only possible to subscribe or unsubscribe to tables or filter groups. The only exception are some fields related to the transmission that can be changed per subscriber like the Full Table Transmission to e.g. re-send again all the data and the Data Expiry Time Span Formula explained before.

The Link to action on the Data Distribution Administration page provides a way to sync the setup of one or more subscribers (child) to one subscriber (parent) so that they share a common set of tables and that only the change of the parent subscription is needed instead of changing all subscribers.

.

1.	. Select the subscriber (parent) which does have the subscription of tables you need. ⇒ . Fig. 37: Link to on Data Distribution Administration page
2.	. Click on the Link to action. ⇒ The list of subscribers opens:   . Fig. 38: Select Subscribers
3.	. Select the subscriber(s) (child(ren)) you want to link to the previous selected one (parent) and click OK.   To select more than one subscriber (child) keep [Ctrl] pressed, while you click on the subscriber lines. ⇒ On the Data Distribution Administration page you can see the selected subscribers (children) linked to the one above (parent) by showing the link in brackets next to the subscriber no.   . Fig. 39: Linked Subscribers

Both subscribers (19+20) are now linked to subscriber 18. They are indented to the right and displayed immediately after the parent subscriber. The No. includes the No. of the parent between brackets, e.g. 19 (18). Moreover, both have now the same count of table subscriptions (7) as its parent which indicates that they have the same set of subscription to tables and filter groups.

Any change on the subscriber 18 (Subscribe/Unsubscribe) on tables will be synched to 19 and 20. This is also applied on Filter Groups level.

While a child is linked to a parent, no change of subscription should be expected in the child. However, in that case it is possible to break the link to the parent by confirming the message in the following screenshot, after clicking Subscribe or Unsubscribe.:

.

Fig. 40: Break link to parent

You can also use the action Remove Link to break the link from the selected child subscriber to the parent subscriber:

.

Fig. 41: Remove Link to parent

The subscribers connect periodically to the publisher to download and process the data and send information about the status of the process. This information is stored in the transmission log in the publisher.

The Filter Groups at the bottom of the Data Distribution Administration page displays some additional information in terms of the transmission log:

.

Fig. 42: Transmission Log Entries

.

Field	Description
No. of Transmission Logs	Count of the transmission log records related to the Filter Group for a specific table and subscriber. The lookup leads to the Transmission Log page: The screenshot above displays the log records which are generated in case of a successful transmission. The possible types are: Transmission: the subscriber has connected to the publisher and the data has been downloaded. Processing: the data download has been completed and the data is being processed/updated in the related tables. Post-Processing: the data process has been completed and the post-processing routines have been completed. This type of record is only generated in case there is an object setup for post processing.
No. of Completed Transmissions	Similar count as No. of Transmission Logs but filtered by the status “Completed”.
Type (Last Transmission)	Displays the Type (Transmission, Processing, Post-Processing) of the last transmission.
Status (Last Transmission)	Displays the Status (Started, Completed, Error) of the last transmission.
Entry No. (Last Transmission)	Points to the last transmission entry in the Transmission Log.
Last Transmission Timestamp	Displays the Entry Timestamp of the last transmission.

The incadea Automotive365 Network Management (Publisher) app includes the permission sets as follows:

.

Fig. 43: Permission Sets

This is the basic permission set. The aim of this permission set is to provide access to the necessary objects involved in the table data modification detection. Thus, all users must have this permission set assigned since potentially any table can be used by the app to transfer to the subscribers.

When the app is installed, this permission set is assigned to all users automatically. For new users once the app has been installed, the admin must assign the permission set to the new user directly or by including it into a user group.

The basic users do not have access to the Data Distribution Administration or any related logic.

This is the admin permission set. The aim of this permission set is to grant admin users access to all functionalities of the app including the Data Distribution Admin Rolecenter. Technically, this permission set includes the basic one INCA365 DDP.

This permission set must be assigned manually by an admin user.

This is the permission set used by the Azure Active Directory Application and provides access to the subscribers which conmue the OData REST APIs exposed by the publisher. To assign this permission set please see ⇘ “Create the Azure Active Directory Application in Business Central”.

Technically, this permission set includes the basic one INCA365 DDP.