Server Connect Names In A Flow

More helpful Flow questions:

  1. Do the names of the Server Connects within a flow need to be unique from the ids of any Server Connects outside of a flow?

  2. Do the names of a Server Connect within a flow need to be unique from the names of Server Connects in other flows?

Thanks!
Antony.

(you know how important my Server Connect naming conventions are, @George :wink: )

Simple rule of thumb: it’s never a good idea to use same names/id :grinning:

1 Like

It’s so important to use unique names in your code no matter what. It is good practice and makes changes a lot simpler, debugging far easier, and reading through your code a lot kinder on the eyes. Not to mention all the conflicts having the same ID’s can create, which are numerous to say the least.

:wink:

Hey Dave… yes, I would agree with that…

But my app is huge, and my unique name generator is running out of its capacity to manage unique names, so I’d like to give it a holiday where I can! :slight_smile:

And since Server Connects outside of a flow have an id and inside a flow have a name then I’m thinking this could just be the chance… :thinking:

Oh, and while I am here, thanks for all the wonderful info you contribute on the forum! :innocent:

Best wishes,
Antony.

1 Like

Very kind to say so Anthony thank you. We are privileged to have such a community and each and every member contributes where and when they can. A true testament of Wappler's founders efforts to include us all in decision making, and make us all feel a part of the product. Rarely experienced this camaraderie outside of very close-knit IRC channels!

I know the naming thing can become tedious but just roll with something like 'create_INPUT_user_name', 'update_INPUT_user_name', 'update_FORM_user' etc. I'm forever updating and forgetting to do this but slowly it is becoming second nature, only took a few years!

:smiley:

1 Like

We all have different ways of working and try to invent our own methods but it is always good to see what others do.

I have an Excel table with the following, which is very similar to Dave’s suggestion.

image

Here I’m using DB Table Names and Queries as examples but the logic can be applied to many things including Form Field Inputs etc. Hope this give you food for thought :slight_smile:

I think this makes it even more important to stick to a naming convention and keep IDs unique etc.

Having said that, I would distinguish between unique IDs and unique names. I often use the same name more than once on a page. Eg I'll typically have a modal containing an insert form, and another containing an update form, on the same page. I'll use the same names for both forms. I don't think there's a problem with this, and it keeps things simpler.