Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Issue during build upgrade

Avatar

Avatar
Validate 1
Level 2
dboat
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
dboat
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
dboat
Level 2

13-03-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

369 likes

Total Posts

726 posts

Correct Reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

369 likes

Total Posts

726 posts

Correct Reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Vapsy
Employee

14-03-2019

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

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

369 likes

Total Posts

726 posts

Correct Reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

369 likes

Total Posts

726 posts

Correct Reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Vapsy
Employee

13-03-2019

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

Avatar

Avatar
Validate 1
Level 2
dboat
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 2
dboat
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
dboat
Level 2

14-03-2019

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.