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

In-cotext not working for DCT with tabs

SwatiM

Hi

We are trying to implement In-context editing for DCT with tabs. But when we click on any item in a DCT, whole DCT is opening up and not an indivdual field.
Any Suggestion?

Find more posts tagged with

Comments

Bhargav Coca

What version of TS and you need to Post your DCT to check where you were going wrong.

Thanks

Rick Poulin

You should also post your in-context-edit attribute value, since it sounds like your XPath isn't matching up with a field in your DCT.

SwatiM

@lilleywhite:- Teamsite Version , Autonomy Interwoven TeamSite 7.2.1.0.0

DCT :- A sample DCT is attached here.

There will be no tab structure in xml if location attribute with tab is also given
XML created with this DCT will be:-
root
c1
item1
c2
item2

@rpoulin:- tabs does not create XPath. InContext-editing problem is with implementation of tabs only. It Opens whole DCR.

Rick Poulin

@rpoulin:- tabs does not create XPath. InContext-editing problem is with implementation of tabs only. It Opens whole DCR.

I think you misunderstood what I was getting at. Ultimately, your component has to have an element with an in-context-edit attribute listing the field(s) that you wish to see in the popup. You must list all items and/or containers individually. If you want to show the whole tab, you should put a container around all of that tab's contents and then use the XPath to that.

If you believe your in-context-edit attribute value to be correct and it still doesn't work the way you were expecting, post its value.

expression.jpg

SwatiM

In-context attribute value for item1:

"div in-context-edit="{/Properties/Data/Datum[@Name='sample-dcr']/@ID"}" dcr-item-paths="/root/tab1/c1/item1""

Rick Poulin

Well that's looking ok except.. have you tried removing the tab from the path? i.e. dcr-item-paths="/root/c1/item1"

SwatiM

Yup...no Xpath is coming for tabs ....so the Xpath created for mentioned example will start from root container and then container inside tabs and so on.......
As tab is not coming in the path so thr is no need to remove it from path.

Rick Poulin

Yup...no Xpath is coming for tabs ....so the Xpath created for mentioned example will start from root container and then container inside tabs and so on.......
As tab is not coming in the path so thr is no need to remove it from path.

What? That sounds backwards. Since the tab is not part of the xpath, having it in there causes your path not to match the item, leading to the problem you're seeing. You would HAVE to remove it from the path for it to match.