Agreement Extension Value Not Loaded After Save

[Former Member]

We have created a couple of extension definitions in the Agreement (1003) extended class.  When creating a new subagreement and populating these fields with values, after clicking the Save button, the values still appear.  Even after clicking Done and going back to the Agreements tab on the master agreement, we can immediately reopen the subagreement and the fields are still populated with the values.

Once we save and come out of the master agreement and then go back in, the extension field values are gone.  This occurs even if the exension is a required field.  The weird thing is that if the value is re-entered and then saved again, the value is retained when reopening the subagreement.  It seems to only get "lost" after the first save and getting completely out of it.

We are currently on Application Version: 7.0.01.08 build 70219:2011-07-12 09:03 EDT but we are in the midst of upgrading to Application Version: 9.0.05.00 build 156948:2012-10-02 17:12 EDT this week.  Go-Live is on Sep 30, 2013.

We have this issue in our QA and prod environments, but this does not occur in our dev or sandbox.  This happens in both 7 and 9 versions.
(QA is version 9 and prod is version 7).  This is happening for all extension fields created for agreements.  Also, we've created variables based on these fields that are used in our contract document templates during contract document generation, so when we create a new contract document, these variables are unresolved.

Does anybody have any ideas??  We are in a time crunch now to release the upgrade and this needs to be resolved ASAP!

[vikram_shanmugasundaram]

Hi Arlene,

I suspect this is script related. I’d take a look at the logs first and see if there are any scripting related errors. I’d also compare the scripts in QA/Prod and Dev/Sandbox to see what is different.

Another thing you could try is to turn off all the scripts. Manually populate the extension fields on the Agreement and see if you are able to reproduce the problem. At least this will tell if the problem is with the scripts.

Hope this helps.

Regards,

Vikram

[Former Member]

Vikram,

We already tried turning off the scripts and manually populating the extension fields and the same thing happened, so we are confident that it is not the script.  We also confirmed that the scripts are identical.  We are planning to clear the logs and run the scenarios again in QA and Dev this morning and comparing the logs.

We suspect that there must be something different in the environments for it to work perfectly in two of them and not work in the other two.  We’re hoping that any environment change will be simple because we don’t have the resources or time to re-install them and then worry about restoring the data from an original environment to a newly installed one.

-- Arlene