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

Capturing generated file location in DCR

cmatsyk

Is there a way to trap the file location where you generated a file to in the DCR? I would like to deploy this value to the database to drive my navigation.

Thanks in advance...

Colin

Find more posts tagged with

Comments

kaalraa

Is there a way to trap the file location where you generated a file to in the DCR? I would like to deploy this value to the database to drive my navigation.

Thanks in advance...

Colin

Could you please provide some info:

1. How are you generating the output file; generate button / iwgen / external task?
2. What is the TS version you are using?

nipper

Is there a way to trap the file location where you generated a file to in the DCR? I would like to deploy this value to the database to drive my navigation.

Thanks in advance...

Colin

You mean change the DCR after you generate the output ? You could, is it a stellar idea, not really.

However you can attach an extended attribute to the DCR with the file that was created. This is implementation specific, if you use workflow to specify where the generated files go (i.e. users cannot change the name/location) then attach the EA in your generate_html script. If users can change the filename/dir of the output file, then use the TPL to attach the EA.

Either way, you can deploy the extended attribute to your DB via datadeploy (or a script if you do not use DD).

HTH

me

gzevin

This is implementation specific, if you use workflow to specify where the generated files go (i.e. users cannot change the name/location) then attach the EA in your generate_html script. If users can change the filename/dir of the output file, then use the TPL to attach the EA.

not only that. Many of forms that are done these days have that information in the DCR. i.e. DCR name plus output file location can predefine basically everything and FormAPI will write/generate all the files.

rahulindia

You can set output file names as an extended attribute to DCR

ShowTablesSelectedInParameter.rptdesign

maru

I'm working in something more or less related to this.

My DCRs don't have as EA the path and name of generated HTML file, then right now i'm trying to optimize a function that goes to html folder and looks through all this folder and subfolders for a file that matches Templatepath and DCRname just that it's taken too long looking for the file, because, obviously i've got too many html files.

Is there any way that i can get the path and name of HTML file that was generated from an specific DCR?

I'm working in TeamSite 6.7.1 SP1 under windows environment.

Thank you.

gzevin

I'm working in something more or less related to this.

My DCRs don't have as EA the path and name of generated HTML file, then right now i'm trying to optimize a function that goes to html folder and looks through all this folder and subfolders for a file that matches Templatepath and DCRname just that it's taken too long looking for the file, because, obviously i've got too many html files.

Is there any way that i can get the path and name of HTML file that was generated from an specific DCR?

I'm working in TeamSite 6.7.1 SP1 under windows environment.

Thank you.

as I described above, a good way of doing this is to map the DCR location to the HTML location, so, you always know the path of your DCR so your TPL can determine the output path. If your business requirements as to how to map your DCR to HTML are different, then you have to work out some different ways.