Methods of Programatically Updating Dataset Rules
Our client has created around 1350 datasets that need to have their Repo and File Path changed as part of a applictation migration. All of the sets of changes are the same: Changing the FilePath and the Repo. I'm looking for a programatic solution, preferably a detailed one. I know that general structure is likely something along the lines of "Obj-Open, Property-Set, Obj-Save" but given that this is manipulation of a actual pega rule and not a instance of a created class, I have reservations and a non-perfect understanding of anything else that might need to happen. (IE, any validation, any special rules around creating a new instance of Data-Admin-DataSet-File)
Our client has created around 1350 datasets that need to have their Repo and File Path changed as part of a applictation migration. All of the sets of changes are the same: Changing the FilePath and the Repo. I'm looking for a programatic solution, preferably a detailed one. I know that general structure is likely something along the lines of "Obj-Open, Property-Set, Obj-Save" but given that this is manipulation of a actual pega rule and not a instance of a created class, I have reservations and a non-perfect understanding of anything else that might need to happen. (IE, any validation, any special rules around creating a new instance of Data-Admin-DataSet-File)
To shortcut a few questions that will likely be asked, in an attempt to come up with a better solution then updating a thousand data sets: 1. Can't we update the Repo the current Datasets are pointing at? No. This is a Pega Cloud Env. The new repo to be used needs to be the default S3 repo, and we were informed that we cannot update a non-default repo to point to that location. 2. Is it necessary to update all of these data sets? We do not have a "short list" of important ones, or any other criteria to identify which ones need to be updated and which don't. We do not have the time to redesign the clients solution to use less data sets. We have tried to consider any clever/useful solutions that we would normally go with to avoid this level of effort, but I can say with a fair level of confidence that there is no magic bullet/redesign availible to us at this time, hence the need for manual/programatic updates. At a high level, I'm looking for a reference activity that does this. It doesn't matter if it's something OOB, or something that was custom made for similar purposes.