Bug report: passing reference-type action parameters between views

Ask the community
1

The issue described by the free ask assistant:

Issue: When triggering an action from a button in a drawer/different view and passing App Variable references (cardinality ONE) as action parameters, the Create Object action nodes throw warnings:

Skipping value. Got array, expected single value.

Setup:

  • App Variables: Selected Goal and Selected Challenge (both reference type, cardinality ONE)

  • Icon button in Quick View drawer passes these as action parameters to “Discussion - Start Discussion” action

  • Action creates Thread and Strategic_Audit_Log entries with Context Goal and Context Challenge properties

What we tried (all failed):

  1. :white_check_mark: Passing App Variables directly as action parameters

  2. :white_check_mark: Using functions to extract single values from parameters

  3. :white_check_mark: Direct data binding to App Variables (without action parameters)

  4. :white_check_mark: Creating temp data sources and persisting

  5. :white_check_mark: Verified Delete Rule = “None” on all reference properties

Workaround that worked: Removing action parameters entirely and directly referencing App Variables inside the action nodes resolved the issue.

Root cause: The button triggering the action is in a different view (drawer) than where the action executes. When passing reference-type App Variables as action parameters across view contexts, Appfarm incorrectly interprets them as arrays instead of single references.

Question: Is this a known limitation when passing reference-type action parameters across view contexts? Should this be considered a platform bug?

2

Hi Harald,

Thank you for reaching out! I have not been able to reproduce the error, I am able to pass single-cardinality reference-type App Variables into action parameters across multiple views and drawers.

Could you please provide some more detail on how the specific use case is configured in terms of data types and cardinality on the affected object classes (Goal and Thread classes, possibly others if relevant) and the setup of the data binding between the App Variable and the Action Parameter?

//
Jan Einar

3

Thank you for looking into it. I believe this was the real issue:

The Appfarm Build AI made a On Enter call on a Text Edit field calling the action (with the wrong parameters). As this event does not exist in the builder I simply made a new one and deleted the old one with issues. By that the hidden call was removed.

From the log:

The problem: The “Follow-up Input” text edit component is bound to Message (temp).Message (data source AORRMG, property IFfiYo), but when you type a message and press Enter, the On Enter event handler triggers the “AI - Thread - New message in thread (step 1)” action (ID: cmgKLz).

Looking at the On Enter event handler:…