Inquiry regarding task.json ID behavior during legacy import/export

[iti-attunity-sup]

Hello team,

When you perform the steps below, you can confirm that the "id" in task.json remains unchanged after the import:

1. Export the project in legacy format.
2. Modify only the name in task.json and import it.
3. Export it in legacy format again.

Q1. Is it safe to proceed with the execution as is?
⇒ In our environment, it appears to be working properly.

Q2. Is it safe to ignore the id?
⇒ We are checking this because it is also referenced in places such as idToNameMap in building.json.

Thank you in advance for your assistance.

Best Regards.

[Rahul_Kale · Accepted solution]

Hello @iti-attunity-sup ,

Thank you for reaching out to the Qlik community,
 

Q1. Is it safe to proceed with the execution as is?
Yes. Based on your test, after exporting in the legacy format, changing only the task name in task.json, importing it, and exporting it again, the task continues to function correctly, and the original ID remains unchanged. Qlik officially supports editing exported JSON files and reimporting them when migrating tasks between environments. 
 

Q2. Is it safe to ignore the id?
Generally yes, for this use case. The observed behaviour indicates that the internal ID is preserved and is not automatically regenerated when only the task name is changed. Since references such as idToNameMap use this identifier, it is best practice not to modify the id manually and treat it as an internal object identifier. If the task imports and runs correctly, the unchanged id can be left as is.