Forum Discussion

martinmcmillan's avatar
martinmcmillan
New Member
1 year ago
Solved

Value cannot be null. Parameter name: Non-null assertion failure: mFormulaText

I have recently been using the PBIP format via a GIT repo. After a change in the service, I re-Sync'd my files from the workspace and it keeps coming up with the following error when trying to reopen...
  • rajendraongole1's avatar
    1 year ago

    Hi martinmcmillan  - 

    Check your GIT repo for corrupted or incomplete .m definitions:

    Go to YourProjectFolder\DataModel\

    Open the affected table folders (each table should have a .m file)

    Look for any empty or missing .m files (especially for tables created from Query Editor or manual definitions)

    Revert the DataModel and DataModelSchema folders to a working commit:

    Even if you reverted the whole project, verify specifically that the *.m files are not null or blank.

    Restore from a version that successfully opened before the sync/merge.

    Clean and re-clone the repository:

    Sometimes your local repo may cache corrupted metadata.

    Delete your local repo, then re-clone from the remote, preferably from a known-good commit.

    Use Power BI Desktop December 2024 or earlier:

    The March 2025 update introduced more aggressive validation and may break loading PBIP projects with minor issues.

    Try opening the PBIP with an older version and see if it loads.