Hello, What is the easiest way to edit an existing field in a CDT? I have a coup

padmanabhanv over 11 years ago

Hello, What is the easiest way to edit an existing field in a CDT? I have a couple of CDT's in my application which need to undergo some changes(to existing fields as well as add some new fields). I tried deleting the whole list of CDT's and recreated the same by importing an XSD. However all my processes are still referring to the old CDT's(In the data mapping's for eg I can see (username~3) which is obviously referring to an old version). I did go and manually change it - but then all the data mappings in the process got wiped out. There should be an easy way to do this. Please advise...

Discussion posts and replies are publicly visible

0 padmanabhanv over 11 years ago

guess it is this - conf.data.type.designer.namespace
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

In my exported app, one of the CDT's has a namespace of localhost:8080/.../. If I change the default namespace in the server, restart and then import this CDT back again, would it derive the system defined namespace or would it still retain the old one(localhost:8080/.../types) Please help
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

Correct forum.appian.com/.../Data_Type_Designer that is the property and goes in custom.properties.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

Yes, got that, thanks - my question is " If I change the default namespace in the server, restart and then import this CDT back again, would it derive the system defined namespace or would it still retain the old one"
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

The namespace is defined in the XSD and that is the one which has preference over any setting.

The conf.data.type.designer.namespace is just for those data types you create from the UI.

Once a model points to {namespace_1}MY_CDT even if you delete and reimport a CDT with a different qualified name the model will still reference {namespace_1}MY_CDT because the model is independent from the CDT changes that's why Impact Analysis was created but that works only if the CDT is the "same" which means same namespace same name.

Any changes in namespace not planned beforehand will require you to remap your models.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 padmanabhanv over 11 years ago

Thanks a lot ; that was what I was looking for
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel