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

LSCS DCT Attributes

cecilb63

Hi,

I am testing out LSCS and LSDS 7.2 on linux

I find when I publish my existing DCRs to LSCS, my custom attributes are not published. I only see extended attributes. But I've seen 7.2 demo'd before where they added new input fields on a DCR and they were immediately accessible through the the REST API. Does anyone know what I am missing?

Chris

Find more posts tagged with

Comments

Frederik

just a quick guess: I think you can set which EA need to be exported towards LSCS, in a config file under LSCS-Auth folder (lscs-authoring.xml, or so, IIRC)...

vpatel

How are your "custom attributes" stored? As EAs?

cecilb63

Here's a snippet from the DCR.

We are looking for the data associated to the

It is not an EA.

Viral, I remember you demo'd this for us at one time. I thought maybe you had changed some javascript?

Deployment Types Container

Deployment Type
Enter Deployment Type name

cecilb63

Sorry, the tags were not escaped. Here's the snippet again

<container name="cntDeploymentTypesContainer" location="cntDeploymentTypesContainer" pathid="cntDeploymentTypesContainer" combination="and" min="1" max="unbounded">
<label>Deployment Types Container</label>
<item name="txtDeploymentTypes" pathid="txtDeploymentTypes">
<label>Deployment Type</label>
<description>Enter Deployment Type name</description>
<text required="t" maxlength="50" size = "50" />
</item>
</container>

cecilb63

So we are looking for the data associated with the text type, named txtDeploymentTypes

Frederik

I have much to learn about using LSCS, but I don't think it can automatically read off an XML field and make that searchable.

Perhaps the demo you saw had some additional logic implemented to turn a DCT field into an EA automatically. Then I guess the EA could end up in LSCS as an attribute (?)

cecilb63

Am bumping this up because I haven't yet found the answer

Do I have to convert entry fields from the DCR into EA through javascript?

That is the only thing can think of though I have a Professional Services guy here who says I shouldn't have to do that. (but he doesn't know why or what to do beyond that comment)

interDev

Am bumping this up because I haven't yet found the answer

Do I have to convert entry fields from the DCR into EA through javascript?

That is the only thing can think of though I have a Professional Services guy here who says I shouldn't have to do that. (but he doesn't know why or what to do beyond that comment)

Two Cases:

1. If these are existing DCRs, you will have to explicitiy convert the DCR fields in EA. You can use perl scripting to parse the DCR and then can set those fields as EAs. LSCS will read those EAs.

2. For new DCRs, you can use FormAPI (using Callserver) onSave event, to convert those DCR fields to EAs.

I dont think you can query on the DCR content using LSCS.

cecilb63

Thanks

Yes, this has been confirmed, but use EAs with a conversion for existing DCRs

crosstaboutput.PNG