Data bindings corruption

Submitted by Craig on Mon, 01/23/2012 - 12:16
FormMaker hangs after i've editted a partial page then selected the Data Bindings tab. The attached file shows the state FormMaker has got itself into, is there a fix for this?
Attachment
Loading XPaths.GIF

Hi Craig,

Can you provide some more details on what you did before you got this problem?
When you say 'edited a partial page', what screen were you on, and what changes did you make?

Were you able to close and reopen the FormMaker browser tab and get to the Data Bindings screen ok for the Partial Page?

Regards,
Gerard

Hi Gerard
I was on the Page Structure tab where i'd inserted a new BasicTable. I moved the controls from an existing BasicTable into the new one, deleted the old table and then selected the Data Bindings tab so that I could re-link the database record to the new BasicTable. Reopening the FormMaker allows you to edit the partial page again in Field Details and Page Structure but as soon as you select Data Bindings, the whole thing hangs.

Hi Craig,

That does seem strange that you are still unable to get to the Data Bindings tab for this partial page.
Are you able to provide an export of your project (either on the forum or privately) for us to investigate this further?

Also, can you please confirm what browser version you are using?

Thanks,
Gerard

I'm using IE8

Where can I send the export to?

I have a backup from last week but I dont want to restore everything as i've done plenty of work on other areas of the project. If you could tell me which files i'd need to overwrite that would suffice. Is it just from formStructure or xsl_pool as well?

Hi Craig,

I have had a look at the project export, and have been able to recreate the problem.
I think the problem is being caused by the complex hierarchy of partial pages that you have, and the fact that there are multiple routes to get from the Landing page to the Users partial page (and hence all those below it).

In order to work around this bug for now, I would suggest the following changes to remove the multiple routes.

  1. Change the getTeams action to point to the Locations partial page instead of the Teams one.[/*]
  2. Open up the rules for the Teams partial page, and copy them all into the rules for the Locations partial page.[/*]
  3. Add a condition to all the rules in the Locations partial page to check the action name to decide whether to fire.
    All the existing rules should have a condition of /mvc:eForm/mvc:Control/mvc:action[. = 'getLocations'], and all those copied in should have a condition of /mvc:eForm/mvc:Control/mvc:action[. = 'getTeams'][/*]


This change should mean that all the server processing that was happening in the Teams partial page controller now happens in the Locations one, but when finished the Teams partial page will still be correctly displayed when needed.

You should now be able to configure the data bindings ok for all the partial pages, and when you generate and deploy the application it should still work the same.

I hope this helps, but let me know if you have any questions.

We will also continue to investigate this bug, and aim to resolve it for a future release.

Regards,
Gerard

Thanks for that Gerard
I added the Teams route last week and diverted the Ajax submission through it (with no references to the getLocations action). I generated and deployed the application successfully and was deciding which route to delete. It was working fine until I needed to replace the table, two partial pages down the route, in order to remove some inline styling on the table's container div, this was the point at which the multiple routes affected the data bindings.

We use cookies and analytics on our website to support technical features that enhance your user experience.

-