Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
+1
person also asked this
people also asked this
Replies
3 replies
Subscribers
6 subscribers
Views
3519 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Updating Legacy CDT Values
Chris
over 7 years ago
Has anyone had success with updating process instance CDT data that uses a legacy version of a CDT (^1)? We have a production case now where a data type was updated, as well as related actions which utilize Set External PV Activity to keep the main instance up to date. However, with the RA updated to use the recent CDT version, and process instances using ^1, both Set External PVs (using entire CDT) and IFM Manager (using cdt.field, not entire CDT), CLEAR data in the target process instance (no update, just a blank CDT). This is proving difficult since we cannot populate these instances again with query rules, which utilize the latest CDT version and we need ^1. I believe we can cast() with the old CDT version via expression to retrieve data, but since CDT versions are not in synch across Dev/Stage/Production, this is very Band-Aid to get data back in prod but also does not allow updates from the new related ac...
OriginalPostID-271573
Discussion posts and replies are publicly visible
Parents
0
Chris
over 7 years ago
As an update, IFM Manager does work successfully for both current and legacy CDT versions - however some syntax errors may cause the target CDT to clear out. IFM wins the bid here.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Chris
over 7 years ago
As an update, IFM Manager does work successfully for both current and legacy CDT versions - however some syntax errors may cause the target CDT to clear out. IFM wins the bid here.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data