Quite a few fields seem to be receiving uneditable designations of a field type “money” that make semantic type “currency” the only option. This seems to be leading to cases where Q attempts to construct aggregations that, though they would make sense for currency, do not make sense for these measures (many of which are already aggregations that cannot be further aggregated meaningfully. In each of these cases of a locked, uneditable semantic type, the checkbox to prevent aggregation is missing).
I can’t trace this to any characteristic in the underlying datasets or in the databases from which they were constructed (where most of these fields are simply “Decimal (float)” values and “numeric” values respectively, but in the counterfactual case where I could, the documentation appears to suggest that semantic type should always be editable regardless?
Hi @hinkleyp , welcome to the QuickSight community. Can you please change the data type to Decimal (Fixed) in the dataset and refresh your topic. See screenshot:
I would also recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!”
Can confirm that the above step does prevent the automatic categorization of the measure as money. It still strikes me as an undesirable behavior, however, on a platform where float is often a default?
Update: above solution only works in cases where the data type is configurable inside the analysis. However, any calculated field that produces a decimal seems to default to float, and therefore to currency?
