Hi, When trying to pass this code through an on click action on a custom component, it always return true on the if-condition, even though it’s not true. The string that is returned decides which part of the action that is run. Tried detaching the component, and then it works as expected on the exa…

Hi Geir, I have tried to reproduce your scenario without luck. My set up is as follows: I am using a Shared Component which has a Data Type “Action” as a component param. I use this shared component in a view and connect an action to this component parameter. This action has four action params w…

I have changed to logic of the function a bit now, but still encountering the same issue where the exact same code is returning different results on the same data – custom component vs “normal” (detached) component. New code: [Screenshot 2025-09-05 at 10.46.45] The data sources used: v5TEMPAgMe…

Hi again, Thank you for the information. I have tried to recreate the problem, but I am still not able to recreate it. The best way to verify if the filtering works in the custom component is to use console.log to check both the objects and the lengths of the arrays. If possible, we could set up …

Findings from further investigation: Console log for custom component: [Screenshot 2025-09-05 at 12.52.05 copy] Console log for detached component: [Screenshot 2025-09-05 at 12.52.51] Data sources: [88 V5 TEMP AG items] What i am getting out of this, is that the custom component is not reac…

I have been able to reproduce the bug! It seems as you hypothesized, that the custom component is not evaluating the filters correctly. A challenge is registered for this subject and the Devs team are looking at a fix! I will let you know when the a fix is expected, sorry for the inconvenience thi…

Any updates on this?:slight_smile: And do you know if this is something thats been broken from the start of when custom components was introduced, or if it came with the newest update? Would be nice to know in regards to deploying the new version to production.

Hi, the Devs team have investigated the problem and it seems like it has been a prevalent bug for some time. They tested in Create version 118 and it was a prevalent bug here as well. This most likely means, that the bug has been prevalent since the introduction of custom components.

Again, any updates on this? I now have another case where i try to pass a integer through a action param on custom component, and it seems to always return “3” or less no matter how big the number is supposed to be. This in turn makes me spend several hours trying to figure out how and why the acti…

Hi. We are looking into this, but I don’t currently have a timeline for when this will be fixed. We apologize for the inconvenience this bug is causing. We were not aware of the integer issue you reported here, and I was not able to reproduce it in our dev environment. Could you please provide more…

Should have provided more information, sorry about that. A bit to late in the evening to run into bugs… I guess the issue is the same as before with filters not being evaluated correctly. It was just that the filter this time around was a lot simpler than before and it made me believe that this was …

Passing action params through custom components broken?

Bug reports

Olav November 7, 2025, 8:17am 13

Hi! This bug has been fixed in release 123.

Topic		Replies	Views
Error while using an iteration in a custom component Bug reports	4	90	October 23, 2024
Custom UI component - Action with required parameter Bug reports actions	3	110	September 23, 2024
Missing values when only passed to component Bug reports ui	7	118	August 29, 2025
Release Notes 106 Release notifications	6	233	September 25, 2024
Built-in Table filter not working in Custom Component Bug reports	2	61	August 29, 2025

Passing action params through custom components broken?

Related topics