The Data Link is the tool used by T6 to enable data transfer between applications.
For example: A company that has two applications within T6, one for financial control of the head office and another for financial control of a branch. Using the Data Link, it is possible to automatically copy the recorded expense information from the head office application to the branch application, ensuring that both use the same updated data for consolidated analyses.
By using the Data Link tool, we will be able to perform the following tasks:
For the creation and use of this feature, we will need to enable some user permissions.
In Manager permissions, the user will need the following permissions enabled:
To use this feature within T6, it is necessary to use a source application and a target application. Therefore, the user will need to have these permissions for both applications that will be used.
Below we will show the steps for creating and using the data link within T6.
To create a data link, we will follow these steps:
After clicking on edit, a new screen will open where we will configure the properties and mapping of the Data Link;
In an application, there are always 3 scenario options: planned, actual, or closed. The closed scenario will never be copied.
EXAMPLE:
When saving data from a form, the system identifies that we are saving data in a form that serves as a source premise for a data link. It recognizes that there is a data link and already runs it automatically. The data reaches the target, so we have real-time data, which we call online in the product.
By default, all mapping is done by name. Dimensions with different names will be mapped individually;
In the dimension listing we have Source, Target, Total, and Automatically Associate by Name;
The Automatically Associate by Name option will only copy members that have exactly the same name. If the names are different, it will not copy anything.
In some specific cases, a dimension may exist only in one of the applications involved in the Data Link. When the dimension is present only in the source application, it is common to use an aggregator account that covers all members of this dimension, informing in the target application that this level of detail will not be considered. On the other hand, if the dimension exists only in the target application, it is common to select a single representative member, such as Not Applicable, to maintain consistency in the data transfer.
To execute the Data Link, you must have the appropriate permissions in both the source application and the target application.
Under Members, click and select the member;
Under Aggregation, click and select the aggregation type;
Aggregation | Description |
---|---|
Member | Selects only the reference member |
Descendants | Selects all descendants of the reference member |
Descendants (inc) | Selects all descendants of the reference member, including the member itself |
Ancestors | Selects all ancestors of the reference member |
Previous | Selects the directly previous member in the member tree, at the same level as the reference member |
Next | Selects the directly next member in the member tree, at the same level as the reference member |
Previous (Relative to Parent) | Selects the previous member, at the same level and in the same position as the parent of the reference member |
Ancestors (inc) | Selects all ancestors of the reference member, including the member itself |
Same Level Members | Selects all members at the same level as the reference member |
Same Level Members (inc) | Selects all members at the same level as the reference member, including the member itself |
Parent Member | Selects the parent of the reference member |
Next (Relative to Parent) | Selects the next member, at the same level and in the same position as the parent of the reference member |
Previous (Relative to Root) | Selects the previous member in the member tree, at the same level and in the same position relative to the root of the member tree |
Next (Relative to Root) | Selects the next member in the member tree, at the same level and in the same position relative to the root of the member tree |
Parent Member (inc) | Selects the parent of the reference member, including the member itself |
Child Members | Selects the children of the reference member |
Child Members (inc) | Selects the children of the reference member, including the member itself |
Leaf Descendants | Selects all leaf descendants (without children) of the reference member |
Previous Same Root (inc) | Selects previous members in the member tree, at the same level and same root as the reference member |
Next Same Root (inc) | Selects next members in the member tree, at the same level and same root as the reference member |
Previous Same Number of Children Root (inc) | Selects previous members of the reference member, in the same root and with the same number of members |
Data Member | Selects only the Data Member of the selected member |
Descendant Data Members (inc) | Selects all descendant Data Members of the reference member, including its own Data Member |
Exclude Member | Excludes the reference member |
Exclude Data Member | Excludes the Data Member of the reference member |
Next Same Number of Children Root (inc) | Selects next members of the reference member, in the same root and with the same number of members |
Children [Words-DataMember] | Selects only the child Data Members of the selected member |
To remove a member from the list, click next to its name;
Once the member and aggregation selection is complete, click Apply;
After execution, you will receive the result through system notifications, informing whether the execution was successful or if there were any errors;