nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployment from Multi-Select box (list-field)

Scott_G

I'm running into some issues getting these fields to deploy. The documentation on the list-field has me left me uncertain as to how to proceed.

This template has been made as simple as possible in comparison to what we are truly doing, but is still giving me fits in deploying it to our Oracle Database. when it tries to insert to DYNAMIC_HUB_CONSTRAINTS it is not inserting any data. I have tried many different list-field values, this was simply the most recent one.

I would like the table to look like the following when it's deployed:


ASSET_ID                               CONSTRAINT_TYPE      TAG_ID
139d264c-f98a-4c46-a9ae-da1a525165ea   TAGS                 PGSN::00000001
139d264c-f98a-4c46-a9ae-da1a525165ea   TAGS                 DPGSN::00000002
139d264c-f98a-4c46-a9ae-da1a525165ea   UNIVERSAL_TAGS       MTS::K9XBL115

I am able to deploy to both of the other database tables. I'm pretty certain that the CONSTRAINT_TYPE is configured fine, but the value-from-filed / list-field configuration is not correct for the where.value field.


column name="CONSTRAINT_TYPE" data-type="VARCHAR(255)" value-from-element="object/0/displaySections/displaySection/0/criteria/[0-4]/criterion.type/0" allows-null="no" is-url="no" is-replicant="yes"
column name="TAG_ID" data-type="VARCHAR(255)" list-to-replicant="yes" list-field="object/0/displaySections/0/displaySection/0/criteria/[0-4]/where.value" value-from-field="object/0/displaySections/0/displaySection/0/criteria/[0-4]/SelectList/[0-100]/selectval" is-replicant="yes" allows-null="no" is-url="no"

Any ideas on how to configure this properly?

Find more posts tagged with

Comments

sniv

Hey Scott,

It would be great if you put the deployment log file along with config. files.
As it helps to catch exact root cause behind issue.

Can you let me know on which column its failing for you?

Is it for TAG_ID column?

Try to change put >>value-from-attribute<< instead of >>value-from-field<<

for TAG_ID.

Hope this helps you. Do upload log files

Regards!
Vinayak

Scott_G

I am currently unable to attempt that configuration, but will try as soon as I get access to the machine again.

I can't get access to that box for a couple of hours, but will attempt that first thing.

When it goes to deploy and create the rows for the constraint table, nothing is created.

Scott_G

I was finally able to get access again. Changing to attribute did not work, I was not expecting it to, but I did change the deployment configuration as suggested. Attached is the relevant portion of the log.

Edit: There is no error per-se, just the data does not get deployed to the database. The keys match to the configuration, but I believe the configuration of the value-from-field and list-field values are being incorrectly configured.

sniv

Hey,

Log file not clarifying any information related to the wrong configuration.

Even I haven't see any entry for CONTENT_METADATA table.

It would be great if you upload the complete log file for that specific deployment. Also do check with other micro log files , see if you can able to found any thing inside it.

Give one more try by changing the CONSTRAINT_TYPE as

value-from-field ="object/0/displaySections/displaySection/0/criteria/[0-4]/criterion.type

i.e. Remove the /0 from last which comes after the /criterion.type

Regards!
Vinayak

Scott_G

I modified that log file so that it would fit under the size limit. It deploys information to the main table just fine.

I also modified the table to only contain the CONSTRAINT_TYPE and the ASSET_ID; that deployment is working fine. It's simply the configuration with the list-field & the value-from-field configuration.