There is likely an error when retrieving data from the CONCRETE_DESIGN_REQUIRED_REINFORCEMENT_AREA_ON_SURFACES_BY_LOCATION_TABLE, because the surface_no column contains values other than the surface number — as shown in the image below.
Additionally, I am wondering about the necessity of providing the loading parameter to the .get_result_table() method when retrieving Concrete Design tables (e.g. Required Reinforcement). Does it have any significance in this case?
Hi r.sajdak,
can you tell me which version (API & RFEM) you're working with? Also it would be good to have the project or at least a small example project (rf6-file) where I can replicate the behavior. Would you mind to send me one? If you do not want to share the project with everybody, just send a personal message with the project to me. Conversations should always be public, please use this only to send me the project.
As soon I have this informations I'll have a deeper look into it.
Thank you.
Best regards
Robert Milrath
Thank you for response.
I use RFEM 6.12.0012 with corresponding API version 2.12.12.
I attach my model - its a simle model for API testing.
SimpleSlab_Results(copy).rf6 (1.0 MB)
Hi r.sajdak,
I could easily reproduce the issue. It seems that there is something wrong, I already created a bug report (Bug ID=584749) and informed the dev team.
Thank you for the infos and files, hopefully this will help to get this fixed soon.
Best regards
Robert Milrath
Can I find information about this bug status somewhere (and other by ID in that matter)?
I tried in Extranet > Development > Submitted Bug reports but can't find it.
From what I checked this issue is still not resolved. Can someone confirm?
Also I asked before on how to track progress of resolving this issue - where can I find bud status ?
Hi r.sajdak,
I can confirm that the bug has unfortunately not yet been fixed, but we are working on it. Unfortunately, it is not possible to track the status of a bug within the community, nor are bugs reported here displayed under ‘Extranet > Development > Submitted Bug Reports’. However, we do of course try to communicate resolved bugs in the community as well. Otherwise, you can of course also check the release notes regularly; that’s always a good idea, as it ensures you’re always fully informed.
Thank you for your understanding.
Best regards
Robert Milrath
Hi r.sajdak,
thank you again for reporting this issue and providing the example model.
We can confirm that the bug in get_result_table(), where the surface_no column returns incorrect data, is planned to be fixed in version 2.14.1 / X.14.0001.
Please feel free to test it once the version is available and let us know your feedback.
Best regards
