Data bindings - stuck with loading spinner

Hi,

Something has gone wrong with my project, preventing me from expanding data stores, data views on a Routed page, and the cookie manager in Data bindings.

The last line in the log is as follows;

Unhandled rejection TypeError: Cannot read properties of undefined (reading ‘datastore_cards’)

05fd884d39717d51553aa03ec56b6f62

Any help would be grateful.

Thanks,
Ray

As a guess, this could be caused by the fact that you are using the datastore for a document that has a different ID to the one that you used to create the data store schema.

When you create the schema in a document with an ID of index, then this is the result

image

When using the schema on the about page, then the ID should be changed to index.

Hi Ben,

Thanks for the suggestion.

I updated the ID on the routed page to the same as the primary document ID(admindashboard) and still have the spinner of death.

You can see that the Schema editor is showing admindashboard.

I’m at a total loss.
It’s the same for Cookie manager and Query manager.

Thanks for the suggestion. It was worth a try.

Ray

@ryanmorrow might have the same issue with the Form component

I consider this to be a bug

@patrick Would you have any suggestions?

Related to @ben’s suggestion, I would check that the values which should appear exist in dmxAppConnect\config.js.

I’ve come across this issue a few times and I think it’s always been solved by editing config.js. If this resolves the problem, I don’t think it’s a bug. (Normally, it’s not necessary to edit config.js, but if you mix up IDs or change their names etc, things can get in a muddle.)

2 Likes

Hi Tom,

Thanks for the information you provided.

I checked dmxAppConnect\config.js, and it seems that I was missing the relevant data relating to the elements that wouldn’t load. I pulled a commit from GIT which did include the missing data, and now no more spinner of death :wink:

Thanks for your help Tom.

1 Like

@TomD just tried a Git pull and did not resolve the issue.

can I get a better idea as to where this would be in the config.js file?

I think data is appended to this file in the order that properties are assigned in the various App Connect panels (Data Store, Cookie Manager etc). In your case, if you search for sessionStorage, you’ll see the relevant values (or not see them, if they’re missing).

Thanks for your help. Good news is, I created a copy of the files pages in a new project ran the session and API post and it worked. Now I just need the sessionStorage to work on the original files and I can then take a deep sign of relief.

1 Like