I'm using UniqueValues along with other formulas to get my result.
It working fine in database, but not in Runtime.
Is there an alternative solution ?
Well, you can certainly write a custom function.
Or use a plugin like the MBS FileMaker Plugin, as there is a function List.RemoveDuplicateItems which may help to remove duplicates.
How reliable of the custom function ?
You can write one which processes items in the list recursively one, by one.
For each check if it exists in a list and only add it if not.
Than pass back that list as needed.
I did some checking in Help and could not find any documentation of this limitation for runtimes. I then created my own test runtime and yes, I get a ? result instead of a list of unique values from this function.
This would then seem to, at the very least, be a "documentation bug" as they do not appear to have documented the fact that UniqueValues does not work in runtimes.
This is irritating to say the least. Other features missing from runtimes are clearly to limit the option's utility so that it can't be used in place of FileMaker Pro applications as clients of a network. I understand that and do not protest that. Others would likely cost FileMaker a lot in licensing fees (such as saving as PDF). But this is a simple straight forward function that, at least from the outside looking in, looks like a function that would have to be specifically disabled to keep it from working in runtimes. Doing so makes no sense, though I admit that I am not privy to any inside info that might have caused FileMaker to decide not to implement this function in runtimes.
What it does is create the impression that they plan to marginalize runtimes until we all stop creating them (and arguing in favor of them) due to lack of usefulness. I do not state that this is what they are doing, only noting that this is the appearance created by the minimal support provided for this feature.
Yes, Runtimes have been "on the bubble" for quite awhil with FileMaker indicating that they will deprecate runtimes in a future version with many developers, myself included arguing that they are needed both as a source of income for our own ventures and as a way to increase sales for FileMaker. But let's not subject it to "death by neglect". Either support the feature as fully as possible or deprecate it. Don't kill it off an inch at a time.
The online documentation does say that.
Aii I get is number 1 as for the value.
FileMaker Pro 16 Help
Notes •If you set the locale parameter to Unicode_Raw, this function will distinguish between values based on their Unicode numeric encoding, which for example, differentiates between characters with different case and diactrical marks.•This function is not supported in runtime solutions and returns "?".
•If you set the locale parameter to Unicode_Raw, this function will distinguish between values based on their Unicode numeric encoding, which for example, differentiates between characters with different case and diactrical marks.
•This function is not supported in runtime solutions and returns "?".
Retrieving data ...