New to Bubble (few weeks). It´s going well and but now I see that I need some help.
Databases (for this question):
Contract (think of them as job offers)
Name
Consultant (people that potentially could get one of the contracts)
Firstname
Pipeline (who consultant is in process with which contract)
Contract-UniqueID
Consultant-UniqueID
Status (e.g if Consultant is pitched, to interview etc)
One Contract can have many Consultants and one Consultant can have many Contracts.
I am at the stage were this works, I can add Contracts and Consultants and update the Pipeline.
But:
Is this a good structure for Bubble. I tought I should have created a PipelineContract (datatype Contract) and PipelineConsultant (datatype: Consultant) instead of the unique IDs, but I am not able to store both when I e.g add an Contract with the Consultant to the Pipeline database - only the “Parent´s group Contract e.g”
Should I add Contract Name (with the rest of the Contract fields) + Consultant Firstname (with the rest of the Consultant fields) to the Pipeline. This will solve it as I can then just look up everything there - but this seems like a bad database structure (duplicates in Pipeline).
If I keep the above structure I have trouble to understand how to get e.g all Consultants (firstname) related to one Contract. Should be easy in my mind, but not solved it yet (tried alot).
I am NOT a fan of doing stuff like this. I’d rather you just do a search for your Consultant’s name where ID equals the Consultant-UniqueID.
You also open up a slight problem where the consultant needs to change their name. Then you’d need to update all their Pipeline rows with the new name. This would NOT be a big deal, but if you start duplicating data like this for the sake of convenience/performance, you start having to do these types of bulk updates a lot.
Other than that, your db structure seems pretty fine.
This implies that you’re using text fields here to store the unique IDs, rather than fields of the datatypes themselves…
Whilst this will work, it just makes things more complicated (and probably less performant) as you’ll need to make additional searches, and cant access the fields of the Contract and Consultant datatypes directly from the pipeline datatype, without doing additional searches…
Is this a good structure for Bubble. I tought I should have created a PipelineContract (datatype Contract) and PipelineConsultant (datatype: Consultant) instead of the unique IDs, but I am not able to store both when I e.g add an Contract with the Consultant to the Pipeline database - only the “Parent´s group Contract e.g”
This is a better way to do it than just storing the uniqie IDs a texts…
I’m not sure what you mean by not being able to store both when you add a Contract etc…
Surely if you can store the unique ID then you can set the actual datatypes instead…?
PipelineConsultant = SearchBox’s ADD PIPELINE’s value
…that’s obviously assuming the SearchBox Add PIPELINE is of type Consultant (which based on the name of it, I’m not so sure it is… but in that case I can’t work out what you’re trying to do at all?!!)…
Thanks - that worked. Why did I not ever try this - sometimes I think I suffer from brain damage I tought it would store the input box value (Consultant´s name).
If I stand in a Contract (show contract view) how would you suggest the search for Consultants related to that Contract would be? To list all Consultant for one specific (current) Contract.
Assuming the database structure you outlined in your first post, you’ll need to do a search for Pipelines (where the Contract is the specified Contract): each item’s Consultant (that will give you a list of Consultants)…
I’m not sure I understand what the second image is meant to be?.. (you don’t want to do additional searches inside the RG cell…)…
If you’re trying to display the current cell’s Consultant’s firstname in a text element, the text should just be Current Cell's Consultant's firstname (don’t do another search)…
I tought it would store the input box value (Consultant´s name).
