avatar image
1
Supported level of importing related data
By Created , last editted

Hi,

I am wondering how the import function works with related data (belongs to)

Scenario

Model A (Product): model I perform the import.Has properties for number and Name. It has also a Belongs to relation to Model B.

Model B (Category): model with properties Code and Name. It has a belongs to relation with model C

Model C (Category Manager): Model has properties first personnel number/last name.

Findings:

Importing  an XLSX file with the following columns and configrations

Product number (deduplicate) product name (update), category code (deduplicate), category name (update), personnel number (deduplicate) and name (update)

Is giving me this:

1. Product is created or updated

2. If Category does not exists based on the code, it is created in Model B and linked to Model A as stated in the import file.

3. If Category does exists it will not create but also not update category name although it differs in the import file. So in other words it will be skipped.

4. When a category is created a category manager value is shown in Model B in the back-office in the related field, but the object itself is not created in Model C.

So based in these findings I am looking for more insight how Betty handles imports of related data of this kind and what level or depth of relations it will support.

Thanks in advance.



Hi,

I am wondering how the import function works with related data (belongs to)

Scenario

Model A (Product): model I perform the import.Has properties for number and Name. It has also a Belongs to relation to Model B.

Model B (Category): model with properties Code and Name. It has a belongs to relation with model C

Model C (Category Manager): Model has properties first personnel number/last name.

Findings:

Importing  an XLSX file with the following columns and configrations

Product number (deduplicate) product name (update), category code (deduplicate), category name (update), personnel number (deduplicate) and name (update)

Is giving me this:

1. Product is created or updated

2. If Category does not exists based on the code, it is created in Model B and linked to Model A as stated in the import file.

3. If Category does exists it will not create but also not update category name although it differs in the import file. So in other words it will be skipped.

4. When a category is created a category manager value is shown in Model B in the back-office in the related field, but the object itself is not created in Model C.

So based in these findings I am looking for more insight how Betty handles imports of related data of this kind and what level or depth of relations it will support.

Thanks in advance.


Answers
Sort by:

Please login to reply to the topic.