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

adding a new field to DCT, effect on existing DCRs

psr

I wasnt able to add the post to existing forum.. last replied by Ghoti.. so creaing a new thread..

[QUOTE=ghoti]Expanding on the last two posts - the basic concepts are these:

the devnet post is so easily breakable .. I just replied to the post & it broke the thread .. not even allowing me to remoev the post.. anyhow posting it again with updates in the post ..===========So thats exactly what my understanding was. But here is the same issue I am facing (bullet #3 above). Its emptying all element values for that tab when opened exiting DCR.I just tried to update dct with new container. Moving existing element to new container in one of the tab.The element was part of another container. So just moved element & added into a new container (at the same level as old) in the same tab. I was expecting empty element value for new element (xpath change). But its breaking whole tab, removing values from all the fields in that tab including original container.Any suggestions?ThanksTS 671, Windows

Find more posts tagged with

Comments

moonkhanna

I wasnt able to add the post to existing forum.. last replied by Ghoti.. so creaing a new thread..

the devnet post is so easily breakable .. I just replied to the post & it broke the thread .. not even allowing me to remoev the post.. anyhow posting it again with updates in the post ..
===========
So thats exactly what my understanding was. But here is the same issue I am facing (bullet #3 above). Its emptying all element values for that tab when opened exiting DCR.

I just tried to update dct with new container. Moving existing element to new container in one of the tab.

The element was part of another container. So just moved element & added into a new container (at the same level as old) in the same tab. I was expecting empty element value for new element (xpath change). But its breaking whole tab, removing values from all the fields in that tab including original container.

Any suggestions?

Thanks
TS 671, Windows

Can you post your old DCT and new one indicating the item you moved..

Adam Stoller

I wasnt able to add the post to existing forum.. last replied by Ghoti.. so creaing a new thread..

the devnet post is so easily breakable .. I just replied to the post & it broke the thread .. not even allowing me to remoev the post.. anyhow posting it again with updates in the post ..
===========
So thats exactly what my understanding was. But here is the same issue I am facing (bullet #3 above). Its emptying all element values for that tab when opened exiting DCR.

I just tried to update dct with new container. Moving existing element to new container in one of the tab.

The element was part of another container. So just moved element & added into a new container (at the same level as old) in the same tab. I was expecting empty element value for new element (xpath change). But its breaking whole tab, removing values from all the fields in that tab including original container.

You seemed to have ignored the comments about not changing the structure of existing elements - I suggest you spend a bunch of time examining a pre-existing DCR and a new DCR and figure out what needs to change to map from old to new and then write a script to process all your pre-existing DCRs to turn them into new DCRs -- this is assuming you didn't just break the new DCT somehow such that it won't work regardless.

psr

You seemed to have ignored the comments about not changing the structure of existing elements - I suggest you spend a bunch of time examining a pre-existing DCR and a new DCR and figure out what needs to change to map from old to new and then write a script to process all your pre-existing DCRs to turn them into new DCRs -- this is assuming you didn't just break the new DCT somehow such that it won't work regardless.

Not really I ignored it. But I thought the IMP part was keeping the XPATH same. Basicaly adding a element is creating issue here (with or w/o container). (Attached DCT change detail).
- removing element "mdkey" from container (do not create any issue)
- Adding a new container "container2" or even any other element (creates a problem).

Yes, DCR conversion will be always a option, but was just trying to avoid that.

Thanks

Adam Stoller

Not really I ignored it. But I thought the IMP part was keeping the XPATH same. Basicaly adding a element is creating issue here (with or w/o container). (Attached DCT change detail).
- removing element "mdkey" from container (do not create any issue)
- Adding a new container "container2" or even any other element (creates a problem).

Yes, DCR conversion will be always a option, but was just trying to avoid that.

Thanks

Correct, the important thing is to maintain the XPATHs which means maintaining existing structure - which by your own admission, whether you realize it or not, you did not do:

From your just posted example - the "old" XPATH for Keywords was something like:[indent]

/container1/0/mdkey

[/indent]and the "new" XPATH is something like:[indent]

/container2/0/mdkey

[/indent]Ergo the structure has changed, ergo the xpath has changed, and thus - unless you physically massage all the pre-existing DCRs, the keyword content (in this example) will be lost as soon as you go to edit any of them.

ISCBorisB

But I thought the IMP part was keeping the XPATH same

What is IMP? A mythological creature? IMP Webmail Client? Something else? Is it too much to ask to use complete words and common industry
Acronyms in the technical Forum?

psr

Correct, the important thing is to maintain the XPATHs which means maintaining existing structure - which by your own admission, whether you realize it or not, you did not do:

From your just posted example - the "old" XPATH for Keywords was something like:[indent]
/container1/0/mdkey
[/indent]and the "new" XPATH is something like:[indent]
/container2/0/mdkey
[/indent]Ergo the structure has changed, ergo the xpath has changed, and thus - unless you physically massage all the pre-existing DCRs, the keyword content (in this example) will be lost as soon as you go to edit any of them.

Yes, mdkey is the only one I was expecting to be empty. The issue is its removing value from element "Name" as well when I open the DCR for edit. The xpath for which is still,

[indent]

/container1/0/Name

[/indent]

Sorry for not being clear on that & offcourse for "IMP" as well.

Thanks

Adam Stoller

Yes, mdkey is the only one I was expecting to be empty. The issue is its removing value from element "Name" as well when I open the DCR for edit. The xpath for which is still,

[indent]
/container1/0/Name
[/indent]

Sorry for not being clear on that & offcourse for "IMP" as well.

Thanks

Well - I don't have the time, environment, or inclination to try to recreate the environment to try to recreate your issue. My guess is that you modified something else or are using an invalid test case - but that's just a guess. If you truly cannot find anything to explain the change through repeated testing, you can always try opening up a support case... but only if you can prove that the functionality should work and fails to do so in a repeatable manner.

AddBlankRowsWithScriptedDataSet.rptdesign

kajjubee

Any particular reason why you are using pathid and location for containers?

psr

Any particular reason why you are using pathid and location for containers?

No special reason. More as a standard practise.

Adam Stoller

No special reason. More as a standard practise.

I think the question was really why are you using both location and pathid on your containers ... containers should use 'location', items should use 'pathid'