New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Appian Exam ACD101 Topic 6 Question 27 Discussion

Actual exam question for Appian's ACD101 exam
Question #: 27
Topic #: 6
[All ACD101 Questions]

Your customer wants to change the name of a field of an existing Custom Data Type (CDT) to match a renamed database field.

The CDT is backed by a database entity, whose data store has the Automatically Update Database Schema option disabled. The old column name was BIRTHDATE and the new column name is DATE_OF_BIRTH.

How should you proceed?

Show Suggested Answer Hide Answer
Suggested Answer: C

When a field name in an existing Custom Data Type (CDT) needs to be changed to match a renamed database field, and the Automatically Update Database Schema option is disabled, the correct approach is to rename the field in the CDT within Appian. After renaming the field in the CDT to match the new database column name (from BIRTHDATE to DATE_OF_BIRTH in this case), you should verify the changes and publish the data store to reflect the updates. This approach ensures that the Appian data model remains in sync with the underlying database schema. Reference: Appian Documentation - Data Types and Data Stores


Contribute your Thoughts:

Julio
24 days ago
I'm with Gilma on this one. C is the way to go, but keep a fire extinguisher handy, just in case the database decides to throw a party while you're renaming that field.
upvoted 0 times
...
Gilma
25 days ago
Ah, the old 'rename the field and hope for the best' scenario. I'd go with C, but I'd also have a backup plan in case something goes wrong. You know, just in case the database decides to rebel against us mortals.
upvoted 0 times
Alberta
2 days ago
User 1: I agree, let's go with C and keep a backup plan handy.
upvoted 0 times
...
...
Lavera
1 months ago
That's a good point, but wouldn't it be safer to make changes in the XSD file first to ensure data integrity?
upvoted 0 times
...
Chau
1 months ago
If the database schema auto-update is disabled, I'd probably go with C. Renaming the field in the CDT is the way to go, just to be safe.
upvoted 0 times
Dean
18 days ago
I think C is the best option here. Renaming the field in the CDT in Appian seems like the safest choice.
upvoted 0 times
...
...
Aaron
1 months ago
I disagree, I believe option C is more efficient as we can directly rename the field in the CDT in Appian.
upvoted 0 times
...
Stacey
1 months ago
I'd be worried about B causing issues with the data mapping. Gotta be careful with that kind of thing. C seems like the safest bet here.
upvoted 0 times
William
10 days ago
Good idea, let's proceed with renaming the field in the CDT in Appian.
upvoted 0 times
...
Sage
13 days ago
Let's go with C then, it seems like the best approach.
upvoted 0 times
...
Devora
18 days ago
Agreed, we don't want to mess up the data mapping.
upvoted 0 times
...
Leah
27 days ago
I think C is the safest option here.
upvoted 0 times
...
...
Lavera
1 months ago
I think option A is the best choice because we need to update the XSD file to reflect the new database field name.
upvoted 0 times
...
Mona
2 months ago
Hmm, this seems tricky since the database schema auto-update is disabled. I think C might be the way to go, but I'd want to verify that it updates the backend properly.
upvoted 0 times
Paz
23 days ago
Let's go with C then. It's better to be cautious with this kind of change.
upvoted 0 times
...
Samira
24 days ago
I agree, C sounds like the safest option to ensure the backend is updated correctly.
upvoted 0 times
...
Laurel
1 months ago
C) Rename the field in the CDT in Appian. Verify and publish the data store.
upvoted 0 times
...
Carma
2 months ago
A) Download the CDT as XSD, make the appropriate changes, and re-upload the XSD. Verify and publish the data store.
upvoted 0 times
...
...

Save Cancel