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

changing dcr's template type creating problems

manugarg

Hi guys,

We are in a big fix. We had to change the document type of some dcrs (by changing the extended attrbutes and copying the dcrs to another directory). Now, when we try to save them, they are giving error of some fields not being complete. It doesn't show anything red, but expanding replicants shows red fields.

If somebody has faced anything similar to that, please help me out.

Thanks in advance,
-Manu

TeamSite Administrator,
GE Healthcare

Find more posts tagged with

Comments

manugarg

I missed one thing, datacapture.cfg is same for both document type.

-Manu

TeamSite Administrator,
GE Healthcare

Migrateduser

Are you using FormAPI? It may be hiding some required fields.

Dwayne

Are the DCTs the same between the new and old data types? I would guess not.

You've probably got some replicants in the new DCT that weren't present in the old one, and you probably set min="1" (or some other non-zero value) for those replicants. So the DCRs, which were valid on the old DCT, are no longer valid.

If that's the case, then I think you've got two options:

1. Set min="0" in the DCT that you moved the DCRs to, if that makes sense for your data
2. Manually (or programmatically) edit each moved DCR, and populate the required fields in the replicant.

This can't happen with a DCR edited "natively" because the UI won't let you delete replicants below the minimum. But since these DCRs already exist, the UI doesn't create replicant instances on the page for replicants that don't exist.

--

Current project: TS 5.5.1/6.1 W2K

Dwayne

sure, post the answer to my question while I'm writing it, and make me look like an idiot.

Current project: TS 5.5.1/6.1 W2K

cars.rptdesign

manugarg

well, dcts for both template types are same except for few additional fields in new template type. Also replicant's minimum value is same (i.e. 0) in both dcts.

Looks like teamsite uses some more attributes. We have set extended attributes only, ie. TeamSite/Templating/PrimaryPT and TeamSite/Templating/DCR/Type. Are there any other attributes except these?

-manu

TeamSite Administrator,
GE Healthcare

Dwayne

Are those new fields required?

If the problem is just that the required fields aren't showing up as marked in red when you first open the DCR, then this FormAPI might work in your init routine (untested - theoretical only)


if (IWDCRInfo.getStatus () == IWDCRInfo.AVAILABLE) // Make sure that a DCR is in memory
{
    IWDatacapture.setHilightMode(true);   // Force highlight more on
    IWDatacapture.redraw();
}

Current project: TS 5.5.1/6.1 W2K

Frederik

I just checked on our Solaris 5.5.2 SP4, and our DCRs only have the EA TeamSite/Templating/DCR/Type.

You also mention TeamSite/Templating/PrimaryPT which I only find on generated files...

I wouldn't say I find it normal that having too many EA on your DCR would cause your problem... but it is interesting you put that EA?

Frederik

I think we probably reached the point where it would be useful if you posted both DCTs, and perhaps the relevant directory structure of /templatedata ... and your platform and TS version :-)