When you submit a specification modeling task, Dataphin automatically parses data lineage, validates change types and content, and runs pre-checks to ensure compliance with submission standards.
Data lineage parsing description
Data lineage is parsed during task submission in the development environment and during publishing in the production environment. Up to 100,000 entries are supported; entries beyond this limit are not recorded or displayed in the asset directory.
Dimension/fact logical table task
Submission details description
For dimension/fact logical table tasks, you can review submission details, pre-check results, and add notes in the Submit dialog box.
Virtual and enumeration dimension logical tables do not support detailed submission views.
-
Submission Content
Submission content includes the task object's name, type, change type, and change details. Change details cover basic information, object information, table structure, physical information, table relationships, computing logic, scheduling configuration, dependency settings, and runtime configuration.
-
Pre-check
Several pre-checks run when you submit a dimension/fact logical table task. If any check fails, the submission is blocked. The following table uses the dimension logical table submission dialog box as an example.
Check Item
Description
Table Structure
Verifies that the table structure is correctly configured.
Computing Logic
Verifies that the computing logic is correctly configured.
Schedule Dependency
Ensures at least one upstream dependency is set, excluding self-dependency. For more information, see Configure logical table scheduling properties.
Runtime Parameters
Checks that local variables have assigned values. If any local variable is unassigned, submission is blocked. For more information, see Logical table runtime parameter configuration.
Cross-node Parameters
Passes variable parameters through to direct downstream nodes. For more information, see Cross-node parameters.
-
Submission Remarks
You can add remarks to the submission, up to 128 characters.
Check item description
After submission, the Submit dialog box displays the check results. The following example shows the dimension logical table Submit dialog box.
|
Check item |
Description |
|
Computing logic |
Verifies that the logical table's computing logic is accurate and complete. |
|
Parameter configuration check |
Lists all parsed variables from the code, including names, types, and current values, to verify that local variables are properly assigned. |
|
Permission verification |
Checks operation permissions for each object in the logical table, including object names, types, permission status, and request operations.
|
|
Change compatibility check |
Checks whether modifications to the logical table model affect the availability of downstream objects or historical data, including renamed references and field compatibility. Note
If compatibility alerts arise and no action is needed, select Ignore Alert And Continue Submission to proceed. |
|
Schedule dependency check |
Checks the task's dependency and output configurations.
|
|
Operation execution |
Initiates the task submission process. Once operation execution begins, the submission cannot be cancelled. |
to request permissions. For detailed instructions, see Atomic metric/business filter task
Submission details description
When submitting an atomic metric or business filter task, you can review submission details and enter remarks in the Submit dialog box. The following example shows the business filter Submit dialog box.
-
Submission Content
Submission content includes the task object's name, type, change type, and change details, which cover basic information, object information, and computing logic.
-
Submission Remarks
You can add remarks to the submission, up to 128 characters.
Check item description
After submission, you can view the check results in the Submitting Log dialog box. The following example shows the business filter Submitting Log dialog box.
|
Check Item |
Description |
|
Repetitiveness Check |
This check verifies the uniqueness of the computing logic based on the active timeliness settings, ensuring no duplicate logic exists. |
|
Type Verification |
Confirms that the output type of the computing logic matches the predefined type based on the active timeliness settings. |
|
Operation Execution |
Examines the variables in the computing task code to verify that local variables are properly set and parameter names are valid. For more information, see Offline mode variable configuration. |