Help with Passing core_id After Form Submission to Display Data in Next View

[rbdwt09]

Hi,

I’m working on a use case where I have a form that triggers a listener bot upon submission. Inside this listener bot, I call another bot that uses the run_integration action to send data to an external API. The API saves the response to a collection and returns a core_id for the newly created record. I’m successfully retrieving this core_id on the frontend via the listener bot.

Now, after the form is submitted, I redirect the user to another view. I’d like to pass the core_id as a parameter in the URL so that the redirected view can use it to fetch and display the corresponding record from the collection.

Could you please guide me on how to properly pass the core_id to the new view and access it there for rendering the data?

Screen recording: https://drive.google.com/file/d/1koknJPNKGTI2IZp_2vXEHAWw1R5B29GT/view?usp=sharing

Thanks in advance for your help!

[barry]

Hello @rbdwt09 -

It’s difficult to tell how you are performing the redirect - can you provide details on how you are attempting to build the path and do the actual redirect?

If you are using signals, you can use the Route signals to include the core_id in the path. For example, you could define a Route Assignment that points to the route that you want to display after integration runs.

One thing I did notice is the HTTP 500 - keep in mind that once an HTTP 500 is encountered, the page will likely not work as expected any longer. This should be investigated to ensure proper operation of the remainder of the page activity. Have you investigated what is causing that and/or can you share the console details and the network tab details of the new_listener request that encounters the HTTP 500?

Hope this helps!

[barry]

Closing per resolution of Need Help Binding params.result from Listener Bot Response to Wire Field for Dynamic Route Navigation - #4 by UES.IO-Support