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

Need to access data from one DCR in other components.

sazzct

I have a need where I have to access a field from a DCR associated with Component X in all the other components prior to rendering. What I was thinking of doing was having a precontroller get the DCR associated with Component X, and get the value, and set a page token.

However I am having several issues.
1. How does the page precontroller know what components are on the page? Is there a class/method to do it? and from there, can I access the component and get the DCR name?
2. What is the easiest way to pass this to other components at render time? setting a page_token? or adding it to the request object etc?

Find more posts tagged with

Comments

liv2luv

I think you are making simple things into a complex problem. If I understand correctly, you can check the DCR value in other components and let your logic run according to that instead of calling a page controller and things like that.

Try in simple and small steps first before you leap onto the complete solution. Hope it helps

sazzct

I don't think I can.
Basically I have component A that references DCRA.
I have component B that reference DCRB, however I need to know access a specific field in DCRA from an external in component B. How does component B even know what DCRA is?
I don't think its simple, unless I am missing something, I am fairly new to this livesite stuff.

Adam Stoller

I don't think I can.
Basically I have component A that references DCRA.
I have component B that reference DCRB, however I need to know access a specific field in DCRA from an external in component B. How does component B even know what DCRA is?
I don't think its simple, unless I am missing something, I am fairly new to this livesite stuff.

Does DCR-B have a reference to DCR-A in it? or is this some arbitrary association that you're trying to construct on-the-fly?

If the former, you should (I imagine) be able to extract the reference to DCR-A from DCR-B and then extract the field information from DCR-A to do with as you please in Component-B.

If the latter, I think you may have to re-think the design / architecture / implementation... I suppose it might be possible for Component-B to find a Component-A on the same page and then do something based on that, but somehow I think the timing and logistics of such a relationship are pretty tricky if at all possible.

Perhaps you need to combine the two components into one - that takes two DCRs and uses information from the first in deciding some aspect of what to do with the second? That would seem a cleaner implementation to me - but I'm speaking purely theoretically as I really haven't done anything with SP/LS thus far.

sazzct

To solve the problem, I did a precontroller that opens the .page file, and looks for the desired components and corresponding DCRS. I was then able to open the DCRS, and set Request parameters to the values in the DCR. Thus making the values 'global' in a sense, and accessible from all the other components.

Stokes

I see why you would do it that way, but reading the encapsulated XML format of the .page file will be brittle. (i.e. a hack)

Why do you need to look at the page file to get the DCR paths? If your components are specifying DCRs in their properties but then using these 'global variables' for display, why not specify the DCR paths as parameters to your controller?

If you keep it as is, I would at least add some controller parameters that specify each XPath you're going for in the .page file. That way when TS gets upgraded and your stuff breaks (the .page file format changes subtly all the time) it will be an easy fix without recompiling anything.

Stokes.

vpatel

I see why you would do it that way, but reading the encapsulated XML format of the .page file will be brittle. (i.e. a hack)

Why do you need to look at the page file to get the DCR paths? If your components are specifying DCRs in their properties but then using these 'global variables' for display, why not specify the DCR paths as parameters to your controller?

If you keep it as is, I would at least add some controller parameters that specify each XPath you're going for in the .page file. That way when TS gets upgraded and your stuff breaks (the .page file format changes subtly all the time) it will be an easy fix without recompiling anything.

Stokes.

Mr. Stokes, "sazzct" is fully aware of the fact that this is a hack and the structure of .page file is subject to change from one version to the next Smiley Happy