I've come across a problem with how computed entities are shown in the Dataflow Query Editor.
The way a computed entity is shown to a user is through the use of a "lightning bolt" on the entity's icon, however, in some scenarios this lightning bolt doesn't appear, even though the entity is "computed". This can cause confusion when saving and closing the Dataflow Query Editor, and a message pops up saying "This dataflow contains computed entities, which require Premium to refresh. To enable refresh, upgrade this workspace to Premium capacity".
Funnily enough, the lightning bolt does show on the "Entities" page after you've closed the query editor. See the following photos:
The way that I got into this scenario is by creating a new blank query (Roles (2)), and inserting the following code:
#"Reversed rows" = Table.ReverseRows(Roles)
This is a computed entity, since it references the "Roles" entity. However, the lightning bolt doesn't show, because I've called the referenced entity directly.
What I've realised is that the only way to get the "lightning bolt" is if you:
Right click on an entity and click "Reference" and then perform your transformations. This will make your M query look like this:
This will then show the lightning bolt, but has added another unnecessary step.
Click "Merge queries as new". This shows the lightning bolt.
Click "Append queries as new". This shows the lightning bolt.
However, from my investigation, any other table functions (e.g. Table.Group or Table.Transpose) that reference an entity directly (rather than via an intermiate step to the M query) don't show the lightning bolt even when they should. This can make it quite hard to diagnose when you're looking at complex queries.