Why is Bubble forcing Send Data to a Navigation action

I am having the user navigated to a certain page in my application. The workflow editor is trying to force the addition of Data to Send? Why? What can I change to stop this.
See attached screen shot.

Probably just a bug in Bubble. Sometimes the work flow debugger gets wonky. I wouldn’t sweat it. If you’re anything like me, I know those two errors are driving you nuts!

1 Like

Usually this happens when the page you’re navigating to has a data type. Could you verify that the target page does not have a data type? That’d help us I think.


It does have a data type. I still don’t think it should be forcing this.

It does have to force this, because if you have a data type for your page, that means you’re referring to the current page’s thing, and it would lead to a lot of bad stuff if sometimes it’s empty and sometime it’s not (Facebook’s profile pages always have a user in them). If you find yourself wishing it could be, then you should have two pages.


So what data go I need to send. I’m really not getting the connection.

Whatever you set the destination page up to be !

If you look under the page edit menu, so right click the page …

You will “Type of Content”. This isn’t just something loose, it means … this page always needs this Data Type.

So a product detail page … would have Type = Product.

Customer edit page = Customer etc

So each of those pages relates to a SINGLE thing.

If you have a list of Products, then you don’t need Type of Content. You just have a list, then when you click on a Product (for example) it sends you to a product page and also “sends” the thing you just clicked on. So when you are on your Product Page … it has all the Product details from when you just came from. Makes it easier.

For whatever reason you have set up this page with a Content Type. It is quite common :slight_smile: You think “Oh ,this page is about Customers, so let’s set it to Customer” … but it is quite specific.

1 Like

Got it. Thanks. In this case the page does not need a content type. So I removed it. Problem solved.

1 Like

I’ve seen multiple posts in the forum asking this question and read them all and I still can’t seem to get an answer on this. There are instances where I don’t need to send data for everything to work, but Bubble still flags it as an issue.
@NigelG makes a good point that at first I was just setting the type of every page based on what it was about, so I’ve removed those that were unnecessary.
Of the ones that remain, the most common one is something like:
User clicks “Add New Request” - Navigate to Create Service Request page

  1. If they click from the existing thing they want service on, data to send is the thing and the page is set to auto-populate accordingly as the default value.
  2. If they click from home page, there is no data to send and it will prompt the user to populate with the placeholder.

What am I missing? Is there a different way I should be doing this?

Pages with data types are usually for logged in Users. If that’s not the case, then let them do whatever it takes to associate that data type.

You can also create a new modal ‘page’. This works similar to any other development environment.

You can also specify the Current User and any table inside of it as the data type, even if they are not logged in :wink:

Thanks for the quick reponse, @nocodeventure.

All my pages are for logged in users :slight_smile: so that’s not the situation here. Maybe more details would help:

  1. Current User has equipment (current user’s org’s equipment list)
  2. Equipment has service request (equipment’s service request list and service request’s equipment)
  3. Service request page is set to type equipment because that is what is needed to pre-populate.
  • If current user is already on the equipment page, equipment data is sent to service request and it auto-populates

  • If current user navigates to service request from header, no equipment data is sent and the user has to select from the dropdown list (which is dynamically populated with user’s org’s equipment list)

Does that help?

I can’t really tell from looking at the information. Maybe it’s a good idea to go back to the manual or basic tutorials.

OK, thanks for trying. Maybe someone else will be able to help.

I’ve done all the tutorials and read though the manual multiple times and it doesn’t really address this situation. This might just be another one where Bubble developers didn’t anticipate the use case and I’ll have to just keep ignoring all the error messages - it’s just that legitimate errors get mixed in, so I was hoping to have it addressed.

I would be tempted to combine the two pages, so have the “detail” part on a Group.

But understand that can a) be tricky to manage b) a lot of work to swap.

A good alternative is to dispense with Page things and use a parameter. Or two.

So pass the unique ID of the thing in a parameter and then on page load …

If there is a parameter do a search, and if found show the equipment.

If it isn’t or there is no parameter then show the placeholder.

1 Like

Thanks, @NigelG. The parameter approach sounds like it might work. I haven’t used parameters so far, so I’ll look into that option instead.

Unfortunately, both pages are pretty full of their own data type and having them combined made for a pretty overwhelming page for users who are mostly on their mobile, so they are much happier with them separately. I’d rather leave the friction on my side than pass it on to my customers. :smile:

That is really all the page thing is doing … sending the unique id and reading it back in.

1 Like

Makes sense. I’ll try it out