Anyone encountered this error. In development it shows all the records, but once the grid is in production, it just displays one record.
In development
Anyone encountered this error. In development it shows all the records, but once the grid is in production, it just displays one record.
In development
Looks like a bug to me…Can the Scriptcase team respond to this please?
Thanks,
Ken
Are you sure the data is the same in both environments?
Does the store details tables have the right Keyid to match up with the Julia Roberts member ID?
The only reason I ask is because the Totals in PROD are different than the ones is DEV
Yes. It points to the same database on the same cloud hosted server. I do not have a separate development or production database.
My application is developed and packaged on my desktop.
And then deployed and extracted on the production server.
The application is compiled in the latest scriptcase version.
It did not happen previously. So this is some kind of a bug with nested grids.
Other grids/forms are all fine and the data is correctly displayed.
Almalinux is the OS where it is deployed on the production server.
So why are the totals different? PROD says 60 DEV says 377
There are 2 records in the database with Julie Roberts name. The issue is not only it shows only 1 record but it also mixes up data of 2 different members with same name.
As I said it works fine in the development environment.
As a test, I removed the nested grid, and deployed it again to production and the grid displays fine.
So’ what is the with the nested grid that is causing the problem in production and not in development environment?
I changed the column to HTML link to bring the store items up. I prefer the nested grid, but leaves me with no choice as my customers want to see the items on their records.
Hopefully scriptcase will resolve the nested grid issue soon.
"The issue is not only it shows only 1 record but it also mixes up data of 2 different members with same name "
That sounds like a serious issue.
What field on the Grid are you using to tie into the Nested Grid. Some sort of MemberID?
Yes I agree, It’s a serious issue if using a nested grid. Something broke in one of the scriptcase updates.
Here’s the 3 fields that link it …