Inconsistent Typecasting Options for Object Properties in Reports

·

when using an object property in a report there's no way to typecast it (see the first image) even though the UI for creating a custom property, which is almost identical, does allow it (see the second image); the UI in the first case should mirror the UI in the latter case

2 comments

Vlad S.
·
·
additionally, it would be useful to have an option (perhaps in the lexicon) to say "when property X is present on event Y you should parse it as a string/number/date/object by default"
Vlad S.
·
·
lol I complained about this exact thing two months ago, and forgot about it