So I have the following session relevance to pull back some statistics for custom content:
(it, multiplicity of it) of unique values of (name of issuer of it) of bes fixlets whose (custom flag of it)
but running this yields a singularity error. From my understanding of this, it should not be possible for custom content to exist within the system without a creator being recorded. Looking up the content that results from the following relevance within the console I see that the creator field is populated with the correct value:
ids of bes fixlets whose (custom flag of it and not exists issuer of it)
After scratching my head for some time, it finally occurred to me that all of the content flagged without an issuer is showing as being created by an operator that no longer exists.
Is there another method to pull back the content creator that handles cases such as this that I can leverage? The data is there (the console shows it correctly) so at least for the “name” property of the bes user object is in the database.
Thanks @itsmpro92 for the relevance plurality suggestion. Yes, that would prevent the error in this case as it would remove those objects from making it into the result set. I would normally however use the default value pattern with output like this so as to ensure those are infact accounted for:
(it, multiplicity of it) of unique values of (name of issuer of it | ”Unknown") of bes fixlets whose (custom flag of it)
I do apologize for the confusion with the question and your solution absolutely would work. I was using that example more for background as I would have never thought that the issuer property would result in nothing for custom content given the console does accurately display a value in the UI.