Release Details
Release name: | AppOps Spring ‘21 |
Version name: | Minor Release 6 |
Release date: | April 15, 2021 |
Prodly AppOps managed package version: | 1.197 |
Prodly AppOps managed package update: | No |
Prodly AppOps cloud-based service update: | Yes |
Resolved Issues
This table lists resolved issues in the April 15, 2021 minor release of Prodly AppOps Release.
ID | Description |
---|---|
AP-3554 | Deploying to the same object in the same org causes a 500 error. When the source and destination was the same org, transformations to the same object were failing. |
AP-3553 | Deploying to the same org with transformations causes a 406 error. When the source and destination was the same org, transformations to another object were failing. |
AP-3551 | Empty batch causes 500 error. Under certain circumstances, splitting batches was creating a batch of size 0, causing a null pointer error. |
AP-3550 | Duplicate record inserted after update fails. Under certain circumstances, AppOps Release was erroneously reinserting the record after attempting to update it failed. |
Release Details
Release name: | AppOps Spring ‘21 |
Version name: | Minor Release 6 |
Release date: | April 15, 2021 |
Prodly AppOps managed package version: | 1.197 |
Prodly AppOps managed package update: | No |
Prodly AppOps cloud-based service update: | Yes |
Resolved Issues
This table lists resolved issues in the April 15, 2021 minor release of Prodly AppOps Release.
ID | Description |
---|---|
AP-3554 | Deploying to the same object in the same org causes a 500 error. When the source and destination was the same org, transformations to the same object were failing. |
AP-3553 | Deploying to the same org with transformations causes a 406 error. When the source and destination was the same org, transformations to another object were failing. |
AP-3551 | Empty batch causes 500 error. Under certain circumstances, splitting batches was creating a batch of size 0, causing a null pointer error. |
AP-3550 | Duplicate record inserted after update fails. Under certain circumstances, AppOps Release was erroneously reinserting the record after attempting to update it failed. |