Attribute sourced by microflow causes bug in report

The microflow sourced field causes the following error once used within a basic report: "user lacks privilege or object not found" The microflow does not show up in the security model, probably this is normal behaviour. Once the attribute is granted read/write access, it reverts back into read access. I assume this to be normal as well because it is a calculated field therefore not physically stored. Does anybody have a clue how to use a microflow sourced field in a dataset?
1 answers

Since microflow sourced attributes are not physicially stored, they are not available in datasets.

Note that microflow sourced attributes should be avoided whenever possible, since they have a huge impact on performance.