One way would be to create your own by combining elements.
I don’t have time to test it out now, but you can use creative ways to do that.
For example, you could create a Python formula in make that generates a random string consisting of what you’re looking for.
You could assign combinations of letters for the first two characters (AA is Jan 1, AB is Jan 2, etc.) followed by the year (24) and a random, padded number (there is a random function in the math functions).
If you can’t figure out how to do any of that, leave a note and someone (even possibly me) will help out.
This is just an example. Your final solution may or may not look like this depending on your requirements.
Module Export - quick import into your scenario
You can copy and paste this module export into your scenario. This will import the modules (with fields/settings/filters) shown in my screenshots above.
Move your mouse over the line of code below. Copy the JSON by clicking the copy button on the right of the code, which looks like this:
Enter your scenario editor. Press ESC to close any dialogs. Press CTRLV (paste keyboard shortcut for Windows) to paste directly in the editor.
Click on each imported module and re-save it for validation. There may be some errors prompting you to remap some variables and connections.
JSON module export — paste this directly in your scenario
Oh, why that ? With the combinaison of month + day + year, and 3 random letters, I thought it was a good option to protect me. Do you have another idea for a 8 digits uuid that limits duplicates ?
One thing to consider (if you’re using the date/month/year) to create your uuid is the number of entries you expect to get in a single day. If you’re expecting 5 entries per day, and you hav 3 random letters, that’s not a big deal and your option would work. If you’re expecting hundreds of entries per day, then it no longer works because your pool of numbers (26 x 26 x 26) may not be enough. You want a significan number of slots to make it highly improbable that you’ll get duplicates.
Of course, there are other ways to do that. If everything is self-contained in your make scenario, you could manage the entries in a data store within make.
Basically, what I’m saying is: ther are many (!!) way to accomplish what you’re trying to do. The best (or the apporpriate) solution requires understanding what you’re working with. We don’t have that knowledge, but you do. So work on that part of the scenario (how many entries will I get per day/month/year) to figure out a uuid approach that will work for you.
Thanks, indeed I had the same thought, that’s why I’m going to start with 8 random digits.
I plan to have about 100 subscribers per day, so it’s safer.
But rather than having 5 numbers and 3 letters, as proposed by samliew’s solution (which works very well!) I would have preferred to have 5 letters and 3 numbers.
Do you know how to adjust this on the Make module?
1. If anyone has a new question in the future, please start a new thread. This makes it easier for others with the same problem to search for the answers to specific questions, and you are more likely to receive help since newer questions are monitored closely.
2. The Make Community guidelines encourages users to try to mark helpful replies as solutions to help keep the Community organized.
This marks the topic as solved, so that:
others can save time when catching up with the latest activity here, and
allows others to quickly jump to the solution if they come across the same problem
To do this, simply click the checkbox at the bottom of the post that answers your question:
3. Don’t forget to like and bookmark this topic so you can get back to it easily in future!
Hope this helps! Let me know if there are any further questions or issues.