MENU
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?
Suggested Answer: C
Get Premium ACD101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
35 comments · newest first
TI
Tish
10 months ago
Definitely not B, that won't work with the schema option disabled!
RO
Rodolfo
11 months ago
Wait, can we really just rename it like that? Sounds too easy.
LO
Louvenia
11 months ago
I agree with Annmarie, C is straightforward!
AL
Alise
11 months ago
I think A is better. Downloading and re-uploading seems safer.
AN
Annmarie
11 months ago
Option C is the way to go. Just rename it in the CDT.
AN
Annita
12 months ago
I vaguely recall that renaming in the record type might not work if the schema isn't set to auto-update. So, I guess I should focus on option C instead.
SH
Shaun
12 months ago
I feel like we discussed the implications of the database schema being disabled, which might mean I can't just rename it in Appian. Maybe I should go with option A?
JE
Jess
12 months ago
I think option C sounds familiar from our practice questions, where we had to rename fields in CDTs. But I’m a bit confused about the verification step.
AD
Adrianna
1 year ago
I remember something about needing to update the CDT directly, but I'm not sure if I should download the XSD or just rename it in Appian.
BE
Bernadine
1 year ago
Hmm, this is a tricky one. With the database schema update option disabled, I'm not sure if any of these options will work smoothly. I might need to double-check the documentation or ask the instructor for guidance on the best approach.
CA
Cassandra
1 year ago
Option B seems like the easiest approach here. If I can just rename the field in the record type, that should update the CDT without having to mess with the database schema. I'll give that a try.
JA
Janey
1 year ago
I'm a bit unsure about this one. The question mentions the database schema update option is disabled, so I'm not sure if option C will work. Maybe I should try option A and download the XSD to make the changes.
PA
Pamella
1 year ago
Hmm, this seems straightforward. I think I'll go with option C and rename the field directly in the CDT. That should update the database schema automatically.
JU
Julio
2 years 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.
GI
Gilma
2 years 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.
ST
Staci
2 years ago
User 2: Sounds good, better safe than sorry!
AL
Alberta
2 years ago
User 1: I agree, let's go with C and keep a backup plan handy.
LA
Lavera
2 years ago
That's a good point, but wouldn't it be safer to make changes in the XSD file first to ensure data integrity?
CH
Chau
2 years 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.
DA
Dalene
2 years ago
C seems like the most logical choice in this situation. Renaming the field in the CDT is the safest option.
CA
Carma
2 years ago
I would go with C as well. It's always good to verify and publish the data store after making changes.
GL
Glory
2 years ago
Agreed, it's better to be cautious when the database schema auto-update is disabled. C sounds like the way to go.
DE
Dean
2 years ago
I think C is the best option here. Renaming the field in the CDT in Appian seems like the safest choice.
AA
Aaron
2 years ago
I disagree, I believe option C is more efficient as we can directly rename the field in the CDT in Appian.
ST
Stacey
2 years 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.
WI
William
2 years ago
Good idea, let's proceed with renaming the field in the CDT in Appian.
SA
Sage
2 years ago
Let's go with C then, it seems like the best approach.
DE
Devora
2 years ago
Agreed, we don't want to mess up the data mapping.
LE
Leah
2 years ago
I think C is the safest option here.
LA
Lavera
2 years ago
I think option A is the best choice because we need to update the XSD file to reflect the new database field name.
MO
Mona
2 years 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.
PA
Paz
2 years ago
Let's go with C then. It's better to be cautious with this kind of change.
SA
Samira
2 years ago
I agree, C sounds like the safest option to ensure the backend is updated correctly.
LA
Laurel
2 years ago
C) Rename the field in the CDT in Appian. Verify and publish the data store.
CA
Carma
2 years ago
A) Download the CDT as XSD, make the appropriate changes, and re-upload the XSD. Verify and publish the data store.