Question
AMEX
US
Last activity: 9 Feb 2016 11:13 EST
DataType - Local Data Storage (data table) - PRPC 7.1.8 - Unable to see/ edit records
Issue:
My requirement is to store a set of records in a data table and delegate it to a Case Manager to easily edit the records.
But as we are no longer have data tables in PRPC 7.1.8 version , We are trying to do it through Local Data Storage but no matter how many records we add, it shows no items.
Also it shows the warning message that a dedicated database table is needed. But I do not want to create a dedicated database table. So Can we fix it to map it to pr_other data table as shown below? or will there be any effect on other classes mapping to pr_other?
Accepted Solution
We are trying to do it through Local Data Storage but no matter how many records we add, it shows no items
>>> Is this a new Data table you created in 7.1.8 and used new Data source?
The dedicated DB table creation failed and that must be because the DB user Pega is configured with does not have the necessary permission to create a table.
When you click the link "here" does it tell you what error it failed with?
Even if the dedicated DB table did not get created, it seems the Data record was mapped to some table - probably pr_other.
Now are you trying to add records from the UI and they don't get populated while the application doesn't throw an error?
Check your logs as that might contain more details. Nonetheless, if the UI doesn't give you an error when adding record, that should be reported as a bug.
AMEX
US
Yes this is a new Data table I created in 7.1.8.
I didn't try to create dedicated data atable. I am just asking if I click on the linke "here" and try to map it again to pr_other will the warning message disappear and will I be able to seee the records?
I am quite sure that the records are getting added because when I open instances for the class mapped to this Data table, I can see those records.
Accepted Solution
pr_other stores all kind of 'other' data and the 'warning' is there for a reason since looking up records on this table will cause performance impact especially since everything is going into the BLOB. So, not showing you records is part of design and will save the system from running into performance issues.
Dedicated tables that hold scalar columns are easy to lookup and is the approach we'd like you to take.
pr_other stores all kind of 'other' data and the 'warning' is there for a reason since looking up records on this table will cause performance impact especially since everything is going into the BLOB. So, not showing you records is part of design and will save the system from running into performance issues.
Dedicated tables that hold scalar columns are easy to lookup and is the approach we'd like you to take.