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

error has occured at server, while trying to generate output file

Amrita1

could anyone suggest on this:
I am getting this error while trying to generate output (html) from the current dcr.
attached is the tpl file.

i tried in many other way. dont know where i am missing.
let me know for any information.

thanks.

Find more posts tagged with

Comments

Phanie

could anyone suggest on this:
I am getting this error while trying to generate output (html) from the current dcr.
attached is the tpl file.

i tried in many other way. dont know where i am missing.
let me know for any information.

thanks.

Dont see the error message in the post.

From your TPL code, FEATURES looks like an container in that case you need to iterate everywhere you want the values to be retrieved from the container or mention the replicant value next to features.

Also if you can, attach your sample dct which you are using here

Amrita1

thanks a lot for your quick response.

error msg is:
An error has occured on server.

attached is a dct.
for test purpose i am just trying with the first fields.

Phanie

I guess you have attached dcr not a dct

Amrita1

attached is the datacapture.cfg.

this is the way dcrs are being saved across our applications, and other tpls are working fine.

is it possible, if the dct has any errors while creating dcrs, then generation will not work?

Phanie

attached is the datacapture.cfg.

this is the way dcrs are being saved across our applications, and other tpls are working fine.

is it possible, if the dct has any errors while creating dcrs, then generation will not work?

Amrita, it looks like you are trying to do work in bits and pieces mode ..

Your dct says datacapture6.0.dtd whereas your dcr is getting saved in datacapture4.5.dtd format -- Interesting

Also now moving to your tpl code .. you are trying to iterate a rootcontainer which is not at all possible. If you wanna test how iw_iterate works test it with CONTENT_ITEM container.

As of now try creating & saving a new dcr and double check if it is getting sved according in 6.0.dtd format then work on your tpl modifying you iw_iterate you should be good then

Amrita1

thanks a lot..I will review it..

thanks again

SampleData.xlsx

ISCBorisB

Your dct says datacapture6.0.dtd whereas your dcr is getting saved in datacapture4.5.dtd format -- Interesting

DCT and DCR are totally different XML Structures. What's so interesting about the fact that they have different DTDs?
In this particular case DCR is of type IWOV, this conforms to datacapture4.5.dtd since (can you guess?) TS 4.5.

Everything is fine here as far as DTDs are concerned

Adam Stoller

DCT and DCR are totally different XML Structures. What's so interesting about the fact that they have different DTDs?
In this particular case DCR is of type IWOV, this conforms to datacapture4.5.dtd since (can you guess?) TS 4.5.

Everything is fine here as far as DTDs are concerned

The posted DCT is, I believe, of type "xml" not "iwov" (note the location and pathid attributes and the reference to the datacapture6.0.dtd)[html]

Content entry for an Features
Used to enter content and select other content.
<script language="javascript" location="template-type" src="features.js"></script>
<script language="javascript" location="template-type" src="../common.js"></script>

FEATURES ID

The FEATURES Primary Key for this Content.

...[/html]However since the DCR appears to be of "iwov" style [html]

TEST

...[/html]- my guess is that the templating.cfg has it defined incorrectly as being of type "iwov" and that's where it needs to be fixed.

Amrita1

Thank you so much for the response.

No luck yet. I changed type to xml, still no luck.
Is it something to do with path?? I tried to capture in my logs, its reading the tpl and getting the values from dcr. Problem is while creating the output.

While saving I noticed its not pointing to the output folder, default shows the path of the workarea.

Thanks.