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; } } }

Unable to access items in inline command

paullieb

We are using an inline command that contains a couple nested containers within the tag. Inside the substitution tag we start with a main container which has 2 additional containers enclosed.
We noticed issues with FormAPI accessing node items within the containers.
If the main container is not present we are able to access the items correctly. Is there a rule using containers inside of tag that we are missing?

ie.: /rootnode/tabname/container1/substitutionContainer/pathid

Find more posts tagged with

Comments

jagadesh

We are using an inline command that contains a couple nested containers within the tag. Inside the substitution tag we start with a main container which has 2 additional containers enclosed.
We noticed issues with FormAPI accessing node items within the containers.
If the main container is not present we are able to access the items correctly. Is there a rule using containers inside of tag that we are missing?

ie.: /rootnode/tabname/container1/substitutionContainer/pathid

The Information is not clear. Enclose your DCT and Form API?
Inline can return item, container or entire DCT as well. It does not have any limitation on that except inline inside inline it wont work

paullieb

Here are some examples from the DCT, FormAPI, and inline command.

Let me know if I can provide more details on this issue.

Thanks!!!

Adam Stoller

I haven't done much with tabs in DCT forms - but I seem to recall that tabs are not part of xpaths - where you seem to be assuming that they are.

Also you don't show how you call the function which attempts to set the event handler - which could be significant.

paullieb

From the Interwoven FormAPI docs:
"If you use the element in datacapture.cfg to enable tab views in a data capture form, you must include the tab name in any absolute paths specified in FormAPI code that refers to items within the tab."

Adam Stoller

From the Interwoven FormAPI docs:
"If you use the element in datacapture.cfg to enable tab views in a data capture form, you must include the tab name in any absolute paths specified in FormAPI code that refers to items within the tab."

Fair enough - but you still haven't shown your overall FormAPI structure (e.g.: how you call your 'init' function)

jagadesh

From the Interwoven FormAPI docs:
"If you use the element in datacapture.cfg to enable tab views in a data capture form, you must include the tab name in any absolute paths specified in FormAPI code that refers to items within the tab."

Yes Tabs are part of Xpath only
You have done some mistake in ur form API code.

Always you should use item/container name in Form API


   IWEventRegistry.addItemHandler("/EBrochure/SEO Attributes/defaultMeta/Seo/PageTitle", "onItemChange", setSeoTitles);
Should be
   IWEventRegistry.addItemHandler("/EBrochure/SEO Attributes/defaultMeta/SEO/PageTitle", "onItemChange", setSeoTitles);

[html]
Your DCT Code:

[/html]

paullieb

I could have sworn we tried that and it didn’t work but I just tried it again and it worked like a charm.
Thank you so much for the help!!!

jagadesh

I could have sworn we tried that and it didn’t work but I just tried it again and it worked like a charm.
Thank you so much for the help!!!

Always you welcome. Can you close this thread