Hi
I am using a custom component in a tree / recursive iterating container
In this component I accept RecursionLevel as a parameter to set some paddings based on how it is nested in the tree structure.
This value only exists if it is also used somewhere outside of my component, if I only pass it to the component, it is undefined in my functions, if I use it outside of the component as well, it magically works.
Marcus
Hi, this looks like a bug,
I was able to replicate this is an internal environment.
I have made an bug request regarding this.
// Erik
Would like to pitch in another percieved bug related to a component and datasources.
I am sending in a question object. In the component we want to iterate over all the answers to this question. We use a datasource from outside the component and set up a filter stating something like this: All answers where questionID=question.ID (component parameter). The perceived bug is that this iteration always returns ALL the items in the datasource no matter what the value of question.ID is. However, if I swap out the question.ID component parameter with using an external datasource for ex. viewpropertyX.selectedQuestion and use that in the filter, the filter works as it is suppose to. It seems to me that component parameters does not work when using filters on datasources outside of the component.
Hope this can be fixed 
Øystein
Hi,
Does your setup look like this?
Here “Bedriftsbruker” can be connected to a “Bedrift”. So I have made a custom component with “Bedrift (one)” and “Bedriftsbruker (many)” as component params.
Inside the Shareable Component, I have made an iterating container, iterating over the “Bedriftsbruker”, with a filter set to “Bedriftsbruker.bedrift === bedrift”
That seems to work in my case (117.0).
Of the ~1600 elements, only 2 are visible, which matches with the data and filter.
Please reach out if that isn´t your case.
// Erik
Hi Erik and thank you for this. Our case is slightly different. The component param is only Bedrift (one), and the component will iterate on Bedriftsbruker (many) which is a datasource from the outside of the component. When you then try to iterate over Bedriftsbruker (many) inside the component based on a filter where Bedriftsbruker (many).Bedrift === Bedrift (one), the filter does not seem to work and the iteration returns all the Bredriftbruker (many) records despite the fact that some of them are not related to Bedrift (one).
Øystein
I see, using that setup, it does not seem to filter.
Will register a bug request for this too.
// Erik
Great. Thank you
Øystein
