Bindings (again!)

Hi kidder,

Without a lot more details on your projects, I+?+?+?m not sure if I can provide any specific guidance I+?+?+?m afraid.

Given you are saying it works properly for one page, but not the other then it would make sense to try and look into what the differences are between the two.

The first thing I would do would be to use the Debugger, and compare the incoming requests when loading in the partial page between the working scenario and the broken one. Any differences between these message structures will hopefully help to identify where the issue could be.

For the partial page calls it would be worth checking the event definitions that trigger them to make sure they are both configured correctly, and are submitting the required data.

It is also worth checking the binding settings for your source pages. As the partial pages are contained in a separate project, you won+?+?+?t see a specific accordion entry for the action being called, so unfortunately there isn+?+?+?t an easy way to adjust the bindings for it.
Instead you should make sure that all the bindings are the same for all the actions that are present, so that these bindings will then also apply when calling the action in the common project.

Hopefully these initial pointers are useful. If you are still having trouble, it would be great if you could provide some more details to help us look further.

Regards,
Gerard

Hi kidder,

Thanks for the additional information.

Given it is only one field that is showing the strange behaviour, I would first check out the submission bindings for that field to make sure they are correct.
Then I would check the submission document structure for the action on which it is failing. Does this document have the correct structure for the date value to be bound to? (Assuming a static structure is being used.)

If these both seem ok, you will need to look at the Debugger trace to see what is happening to this particular date value. For example, is it ending up in the control section of the message, or somewhere else in the document? If it is initially bound correctly, at what point in the processing does it get lost? Etc.

Regards,
Gerard

Hi kidder,

This does sound strange.

Are you able to provide us with some project exports so that we can look into this further? If this is possible, it would be good to see an export for the shared common project, as well as one for a project that is working, and one that isn+?+?+?t.
You can email these directly rather than posting to the forum if required.

Please also let us know details of the field that is not binding, which pages are being used, which actions being called etc so that we know where to look.

If you can+?+?+?t provide project exports, being able to see some full development log traces from the working and broken scenarios would be useful.

Hopefully these details will help us track down what is causing the unexpected behaviour.

Regards,
Gerard

Hi kidder,

Thanks for providing the project exports.

I have been looking into this today, and in my testing I have been unable to get the date value to correctly bind for either of the containing projects!
Is it possible that your published applications are using different versions of the Common project?

I am not sure exactly why, but I believe the issue might be linked to the fact that the date field on the partial page that is not binding has 2 submission bindings defined for it.

The other three date fields on the partial page that do work only have the one submission binding into the Process Variables.

In my testing, if you remove the second binding from the 'broken' field, and keep only the Process Variable one, then it does seem to bind correctly

Does this date field need to have the two bindings defined against it? From a quick check against the two main projects you have provided, there is only one page that might be making use of the second binding location. Could this be adjusted to get the value elsewhere if needed?

Please let me know your thoughts.
I will continue to look into why having the two bindings defined seems to be causing an issue.

Regards,
Gerard

Hi kidder,

Yes, that was the page I thought would have an issue, as the submission document from it does not include the Deadline value in the Process Variables, but does have the alternative binding element in the formData block. This means that by removing the second binding on the field, it won+?+?+?t be bound as expected by this page.

Until the underlying issue has been identified and resolved, I think you have two main options.
Firstly you could change the controller rules for this submission so that it will take the value from the +?+?++unbound+?+?+? section and place it in the correct formData location.
Alternatively, you could add another +?+?++hidden+?+?+? date field (add the +?+?++hide+?+?+? class to it) to the Partial Page in the common project. Give this the same date formats etc as the main one, but set it to bind to the second formData location. Give this field the same page display binding as the date field, and setup an onchange event of the main date field to also put its value into the hidden one.

I hope this makes sense, but please let me know if you have any questions.

I will let you know when I have any more details on the underlying issue.

Regards,
Gerard