Ability to hide Json warnings when structure changed.
The ability to import Json files into after effects and link to that data has been extremely useful.
However, one gotchya is we need to be able to suppress the warning that results when the structure of the JSON changes.
IE When you have a simple json file that contains
Example 1
{
"test": "what"
}
If you import that json file into a project, then modify the json file to:
Example 2
{
"test": "what",
"adobe": "after effects"
}
You will then get a warning "After Effects warning: The structure of the data file for the layer "test.json" has changed.
This shouldn't really be a problem because we arent changing the data while After Effects is open. However the state/structure of the json seems to store with each individual after effects project instead of the after effects session its self.
What I mean by this is I create a After Effects project with Example 1 json loaded into the project. Then save and close After Effects. If I update the json file to be Example 2, while the After Effects session is closed, then I reopen the After Effects project I saved when the json had the structure of Example 1, it seems to remember that structure and then warns about the change.
This is essentially preventing scripts from continuing until the user hits the OK button. We are attempting to load in JSON data that can change in length and size frequently, so this is a bit of a road block for us.

-
Alvan Foote commented
YES! This is a real pain point. Please get this resolved.
-
Matteo Bonera commented
I agree with this request. This could help us a lot!
-
Leanne Bird commented
I totally agree - for those of us using AE Render this error is a real pain and limitation! And, it's a totally unnecessary dialog box. It's a really easy fix for the smart devs on the Adobe team too. Please, Please, Please fix it!
-
Chris Voelz commented
Please...please address this!!
-
Katherine Ducey commented
Yes! Same issue, and it happens every time I open the file, even though the JSON has not changed. I believe it is also preventing my render farm from working as it can’t resolve the pop-up when it run AeRender
-
pharp commented
I would like the ability to silence this error box as well. We have one data file in the project, but a dialogue box for every instance the data file is used. Which is frustrating because you are clicking OK through 10+ boxes.
-
Arie Stavchansky commented
Is this simple fix at least in the queue for development. We realize much is going on with the DVA team, but just silencing the modal will help a great deal.
-
Tom van de Grift commented
Let's try to get this thing going again.
Anyone with the solution to this problem?
-
Yaron Cypis commented
/*BUMP*/
Any updates on this issue? -
victor Pérez commented
Hi, It´s been a while, any updates on this?
-
Anonymous commented
Does anyone have any updates on this?? I'd love to get this problem solved.
-
Mehdi commented
I am also having the same issue.
-
victor Pérez commented
I am also having the same problem, this is a huge roadblock when it comes to automated workflows.
If anyone has found a workaround this issue. please let us know.
-
Marcus Round commented
I completely agree and this is a very high priority for me personally.
The JSON functionality is clearly targeted towards automated workflows and this is a huge blocker for that.
-
Jérôme Zecca commented
Adding/removing an entry from an Array ALSO triggers the warning.
And yeah, the fact that this dialog appears when using aerender.exe is a real bother.
Maybe add a "-continueOnDataStructureChange" argument (to complement the existing "-continueOnMissingFootage"?). -
Anonymous commented
It's even worse than that: keeping the exact same data, but changing the order of the keys is enough to trigger the dialog.
And this even happens when using the aerender command.I hope this gets resolved soon
-
Arie Stavchansky commented
Also wanted to point out that the "structure" of the JSON includes the data type for a specific property key. So if in one instance, the JSON is a String, and in the next it's a Number, AE will still throw this "JSON has changed" warning.
-
Arie Stavchansky commented
Agreed. When AE invalidates linked JSON data, it would be best if there was no modal dialog at all since it is likely that the connected JSON might change frequently.
In my scripts I've tried using the app.beginSuppressDialogs() and app.endSuppressDialogs() but those JSON warnings do not react to that code.
Please allow users to silence the "JSON has changed`" error, and just let expressions fail gracefully as they normally do.
Thanks!