Database locations of fields

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

Hi,

How can we find the database locations of fields?

For instance, an extendedSchemaTable with a namespace nsp has a fieldName with string type.

How do we locate this fieldName?

Replies

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

05-08-2019

Hi,

I am not sure if I got understood your question. But in case, you are looking for the details of a field (of an extended schema), you can check the 'Preview' tab of the main schema. (e.g. if nms:recipient schema has been extended to cus:recipient, the extended field details can be viewed in Preview tab of nms:recipient schema).

Thanks,

Subhajit

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

Thanks, Subhajit,

What will be the value if I need to use it in a workflow ?

will it be nspExtendedSchemaTable.sFieldName ?

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

05-08-2019

Hi,

It should be originalSchema.sfieldName. e.g. nmsRecipient.newField.

Thanks,

Subhajit

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

Thanks, I got your logic.,

nmsOrginalSchemaName.FieldName

(if we provide a name for the field at XML, then it will be Fieldname, otherwise,

system would assign sFieldName, i think.)

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

In addition to this, if I create a variable within a workflow, let say myCode in an activity,

and then later if I want to use this code, then i have to use it as targetData.myCode, am I right?

Then if I need to create a query then I have to use [targetData/@myCode], is this ok?

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

05-08-2019

For a variable in your workflow, you can define it as instance.vars.xxx (considering xxx is the variable name) and use it in your query block as $(instance/vars/@xxx)

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

Good point!

Then, what is the difference of targetData.myCode, [targetData/@myCode], @myCode or myCode ?

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

05-08-2019

May I know, where are you planning to access the fields - query or javascript? targetData is used for Targeting dimension of the workflow.

Avatar

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 3
mustafau3722362
Level 3

Likes

17 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
mustafau3722362
Level 3

05-08-2019

Thanks for asking, from JavaScript, but I will be glad to learn Query also.