Error: The specified column was not found in the context at line 3, column 5

[Eiriksra]

Describe the problem

Error HTTP/500: Internal Server Error.
The specified column was not found in the context at line 3, column 5.

Bravo version

1.0.3 (1.0.8566.15194)

Tabular model

Power BI Desktop, import mode

Power BI

Version: 2.118.828.0 64-bit (June 2023)

Steps to reproduce the behavior

In my case version 1.0.3 totally refuses to even open my model. I've downgraded to 1.0.2. where the model opens just fine and I could leverage the prebuilt date table as well as have it do Time Intellegence on selected measures. I just tried upgrading again to this newest version, but again it refuses to open the model.

Additional context

I'm not at all sure that this is the root of the problem but helped by Intellisense I did notice a weird piece of DAX code in the date template. Rather annoyingly First/Last Year seems to look in all my tables for MIN/MAX (I'd much rather tell it which table to use), but in the end there's an empty quotation mark before referencing ''[Value]. See code snippet below:

VAR __Calendar =
VAR __FirstYear = YEAR ( MINX ( { MIN ( 'Last updated'[Last update] ), MIN ( 'Accounting Period Start'[Min Start Date] ), MIN ( 'Accounting Period Start'[Max Start Date] ), MIN ( 'Sales Headers'[Posting Date] ), MIN ( 'Sales Headers'[RecoveredDates] ), MIN ( 'Sales Headers'[TemporarilyLostDate] ), MIN ( 'Sales Lines'[Posting Date] ), MIN ( 'Value Entry'[Posting Date] ), MIN ( 'TempLostDates'[Date] ), MIN ( 'RecoveredDates'[Dates] ), MIN ( 'Period'[Date] ), MIN ( 'Unposted Sales Headers'[Posting Date] ), MIN ( 'Unposted Sales Lines'[Planned Delivery Date] ), MIN ( 'Unposted Sales Lines'[Planned Shipment Date] ), MIN ( 'Unposted Sales Lines'[Promised Delivery Date] ), MIN ( 'Unposted Sales Lines'[Requested Delivery Date] ), MIN ( 'Unposted Sales Lines'[Shipment Date] ) }, ''[Value] ) )

Screenshots

No response

Anything else ?

Trace Id: 00-88fe0f682c2233339496bb1ddc9d9ba7-7c7f4774176dac4d-00

[albertospelta]

Hi @Eiriksra, thanks for logging this! This is a known issue already reported here #690, we have fixed the bug and today we will release a new version of Bravo that includes this fix.

in the end there's an empty quotation mark before referencing ''[Value]

The strange piece of DAX code you noticed in the date model is valid DAX syntax https://dax.do/TsybPcVyTLUE6K but is reported as an error by Power BI Desktop probably due to a bug in the intellisense

Rather annoyingly First/Last Year seems to look in all my tables for MIN/MAX (I'd much rather tell it which table to use)

You can choose which tables or columns to use via the Automatic Scan parameter, as shown in this image

[albertospelta]

Fixed in version 1.0.4