Choose Workspace> Configuration Management > Data Import Management > Data Import > Table Structure Configuration. The following figure shows the configured data tables.
The table structure configuration list supports viewing, editing, viewing scheduling tasks, and removing. However, table structure configurations imported through APIs (created by API synchronization) cannot be edited or removed.
View table schema configurations
Click View to view the table structure.
Remove table structure configurations
Click Remove to remove the table structure.
If the imported data of the table generates a crowd, or a scheduling task has been set for the table, you cannot delete the table. If you want to remove, you must first delete the corresponding population and scheduling task.
Edit table structure configuration
Click Edit to edit the schema configuration of the table. For more information, see.
For the user tag table, to ID Mapping the stability of the system, the user ID field and user ID type cannot be modified.
If you turn off the Import switch for a field during editing, the corresponding crowd, custom tag, or RFM/AIPL model may not be updated, and the corresponding tag judgment component may fail to execute.
View scheduling tasks
Choose 
/> View Scheduling Task to view the execution records of the scheduling task, as shown in the following figure. Click the 
icon to show the execution status of the table.
For more information about scheduling, see Scheduling tasks. 
Create a relational table
Choose /> Create Relationship Table. You can configure multi-entity association relationships (such as user ID and content ID association) based on the attributes of behavior events, and select groups of people based on these relationships.
For more information, see Filter relational tables.
FAQ
I did not create some data tables on the data import page. What table are they?
A: There are multiple situations:
Custom tags of the same type in the workspace are stored in the computing source to generate a user tag table. The type of the custom tag is the table name, and the creator is displayed as API synchronization.
The included fields are all custom tags of this type. The corresponding field names are set when you create a custom tag. The value type depends on the specific tag definition. Different custom tag fields have different update times. You can manually update a single tag on the Tags page. If you have set an automatic update policy when you create a custom tag, the tag is automatically updated.
You can use these custom tags in the same way as you use other user tags. However, do not edit or delete custom tag tables. Rrow-level permission control is not supported.
Events in the storage space are synchronized to the computing source on the next day after the event is reported. The corresponding user behavior table and order details table are generated. The table names are QT reported behavior events, self-reported behavior events, and self-reported order events. The creator displays the result as API synchronization.
For more information about the fields in the user behavior table, see User behavior table data requirements. The names of attribute fields and statistical metrics fields must be the same as the names of event attributes. For more information about the fields in order details, see Order details.
You can use these tables in the same way as you use other user behavior tables and order details tables. However, you cannot perform operations on the table structure.
These data tables will be imported on a daily basis and finally imported into the analysis source. ID mapping has been performed by Tablestore in real time when the reported data is received.
Modules such as WeChat marketing and social interaction will return user data to the computing source of this workspace. These returned data tables will be automatically added to the table structure configuration list and scheduling task list, and their creators will be displayed as API synchronization.
The WeChat marketing module returns the user tag table of WeChat public number fans, whose data table alias is the corresponding WeChat public number, and the underlying data table name starts with "es_wechat_fans_".
The table returned by the social interaction module. The table alias starts with "social interaction_" and the underlying table name starts with "oem_maiscrm_".
You can use these returned data tables for analysis, crowd filtering, and push. However, do not edit or delete their table structure configurations and scheduling tasks at will.
These data tables will be scheduled and imported on a daily basis, and ID mapping will be performed by the computing source, and finally imported to the analysis source.