Bug with values of external csdb variables

Other discussions about CSPro
Post Reply
Iulian
Posts: 22
Joined: February 2nd, 2022, 5:12 am

Bug with values of external csdb variables

Post by Iulian »

Dear Developer Team,

There seems to be a bug with version 8 of CSPro that does not read the values of specific variables from an external csdb file loaded in memory. It affects an important functionality of drilldown/lookup lists.

The attached provides a simple example for debugging.

Looking forward to receiving your prompt reply if there is fix until a new version is released.

Best regards,
Iulian
LookUpCases.zip
You do not have the required permissions to view the files attached to this post.
Gregory Martin
Posts: 1946
Joined: December 5th, 2011, 11:27 pm
Location: Washington, DC

Re: Bug with values of external csdb variables

Post by Gregory Martin »

You're right that this behavior is problematic in your sample application. However, as soon as I add an item to your external dictionary's record, the problem goes away. It is not expected that a dictionary contains only ID items and no non-ID items, which is leading to this issue.

If there is no other data you want to associate with each dictionary listing, I encourage you to set the ID as the region only and then have a repeating record that lists the districts within that region. That way, instead of doing this:
forcase ASSIGN_DICT where REGION_A = REGION and DISTRICT_VS.codes.seek(DISTRICT_A)=0 do

   
DISTRICT_VS.add(maketext("%d",DISTRICT_A), DISTRICT_A);

endfor;
You would do this:
loadcase(ASSIGN_DICT, REGION);

for ASSIGN_REC do
   
DISTRICT_VS.add(maketext("%d", DISTRICT_A), DISTRICT_A);
endfor;
Iulian
Posts: 22
Joined: February 2nd, 2022, 5:12 am

Re: Bug with values of external csdb variables

Post by Iulian »

Dear Gregory,

Thank you for your reply. Following your advice, we've fixed the issue by adding a blank non-ID alpha-item. But it used to work fine without it in version 7.

Best regards,
Iulian
Post Reply