Issues deleting data type
I am encountering an issue with a data type in PRPC 7.1.9. When I try to add a record to my data table, a popup appears and says "pxCreateRecord API failed". Rather than try to resolve that, I figured it was easier to simply delete the data type and then create a new one. I opened the data explorer, used the menu item and selected "Remove from application" as described here:
I logged out and logged back just in case, then I tried to create a new data type using the same name and same class structure. The error message on that was "this instance already exists". So I tried creating a new data type using "Existing data type" and the data type reappeared, but it had the same problem.
How do I drop a data type and recreate it so that it doesn't have the same issues? Delete the class?
Accepted Solution
Pegasystems Inc.
AU
Data-Admin-DB-Table is exactly the class instance you want to include.
Also the individual instances for the class you're migrating if the intent is to copy data also.
I'm fairly prescriptive in my product rules in order to ensure that everything I'm migrating I deliberately have intended to; However, if you select an application in the product, then tick include associated data, I believe this will include all the necessary rules for the data classes defined in your application rule (All those in your Data Explorer.)
Pegasystems Inc.
AU
Hey Sean,
Remove from application simply removes it from the data explorer for that application; you are correct, you will need to delete the class to 'remove' the data type.
Pegasystems Inc.
US
Thanks Joel.
If I want to migrate the data type from server a to server b, what do I put on the product rule? The only real problem I'm having is with what we called the "data table" in earlier versions. Is it possible to migrate that portion? Isn't that a data object, like Data-Admin-DB-Table? If so, what is the class type for that? It sure would be nice to simply add that to a product and move that over.
Accepted Solution
Pegasystems Inc.
AU
Data-Admin-DB-Table is exactly the class instance you want to include.
Also the individual instances for the class you're migrating if the intent is to copy data also.
I'm fairly prescriptive in my product rules in order to ensure that everything I'm migrating I deliberately have intended to; However, if you select an application in the product, then tick include associated data, I believe this will include all the necessary rules for the data classes defined in your application rule (All those in your Data Explorer.)