Hello,
While performing a build upgrade from 8050 to 8192 we encountered an issue with a custom schema definition which is based in part on a calculated field and was wondering if anyone had guidance on how to resolve it.
Error: The value of key 'b' is not present in return parameters of table 'Tbl_y'
Details of table structure:
Table: Tbl_x Tbl_y Tbl_z
Field: a <> b*
Field: c <> d
Field: e <> f
*b is a calculated reference to a field on Tbl_z, i.e. [FK_Tbl_y_Tbl_z\@name]
<attribute advanced="true" expr="[FK_Tbl_y_Tbl_z\@name]" label="Field b" length="3" name="b" type="string"/>
Post build upgrade deliveries and workflows that tried to leverage information from Tbl_y failed due to the above error.
Any ideas?
Thanks
Solved! Go to Solution.
Hi dboat,
The path as per me should be 8050 >> 8192 >> 8640. As these are huge jumps including a version migration from 6.1.0 to 6.1.1 we highly recommend that you have active consulting working with you on the project (just in case there is a need).
Regards,
Vipul
Hi dboat,
Having checked the internal documentation it seems to be a known bug which was fixed on build 8535. Will recommend you to proceed further to the aforesaid build and see if the issue is resolved.
Regards,
Vipul
Thanks very much Vipul, this is helpful. If I look in our download center I see, in this order
- build 8050 (our current build)
- 8192 (our previous target build)
- 8604 (hotfix)
- 8640
Based on your feedback it seems we should target build 8640, I'm wondering what the upgrade path would be to go from 8050 to 8640. Do you happen to know if we need to install any of the incremental builds listed above or can we just jump right to 8640?
Thanks in advance.
Views
Replies
Total Likes
Hi dboat,
The path as per me should be 8050 >> 8192 >> 8640. As these are huge jumps including a version migration from 6.1.0 to 6.1.1 we highly recommend that you have active consulting working with you on the project (just in case there is a need).
Regards,
Vipul
Views
Likes
Replies