Hi,,,, a question
I need to store 20 character strings of the type "000000000000",... "000100110000" ... "101100110011",... which will be used frequently. The use of these strings will be :
-> extract one of the characters ( ex: red ) and verify its value,...if it is 1 it performs Z, if it is 0 it performs Y.
Question
According to your experience, which recommends me,... I use 20 global variables (one for each string) or a 1 global variable with a json and 20 elements inside ?
regards
Draco
thank you Michael, ...sure, I need 20 strings of 12 characters each, ...I don't know how you get to "infer" that it is possible that I don't need the 20 strings with 12 characters.
I would appreciate any information on whether to use 20 variables or 1 json (global var. - with 20 elements).
For the moment I will use the 20 variables, after all, ...if FM is not able to use 20 global variables without losing performance, ...I should look for another tool to create my solutions.
regards
Draco
i would think storing it as JSON in a variable (or global field) would be much easier than having to reference 20 separate global fields.
Plus JSON provides named pairs so it would be very easy to call the exact code.
Draco . wrote:
I don't know how you get to "infer" that it is possible that I don't need the 20 strings with 12 characters.
I didn't "infer" anything, I asked a question. I have some experience in this area and I don't recall ever seeing a use case quite like this. And If I understood what exactly is being attempted here, I might be able to suggest an alternative. But that would depend on your willingness to listen.
Draco . wrote:
I would appreciate any information on whether to use 20 variables or 1 json (global var. - with 20 elements).
Why do you consider only these two options? Even if you do need those strings, there are other ways to store them. I already mentioned one, here's another: a repeating field with 20 repetitions. Or a repeating field with 240 repetitions - so that each value is addressable separately. You didn't say anything about how these strings will be inputted/modified - and that's an important factor in deciding how they should be stored.
Draco . wrote:
if FM is not able to use 20 global variables without losing performance, ...
I don't think performance plays any role in this.
You could store them in one global field as a return-separated list. But IMHO, it would be better to store meaningful data. Do you really have a decision matrix with 20x20 possible combinations?