Field Parameters

Hi powerbiexpert22​ 

Semantic model refresh wont change existing field parameter. It is calculated table with NAMEOF DAX so refresh recalculate and return same rows with no change of slicers and visuals. It can break if referenced field is renamed from Tabular Editor or deleted. You can test after model change

Hello powerbiexpert22​,

No. A semantic model full refresh should not recreate an existing field parameter.

Refreshing just pulls in new data, it won't delete your parameter. I will only dig into it if something looks off afterward, like a field getting renamed or removed at the source. That's usually what breaks it, either the parameter itself or the visuals built on it.

So if you are only doing a full data refresh, the existing field parameter and its slicer selections should remain. If the model was replaced or republished with a different definition, that's a separate case.

Microsoft docs:
Use field parameters to let report readers change visuals

Data refresh in Power BI

Hi powerbiexpert22​ ,

adding to what ShahRukhSameer said: a full data refresh (via Refresh Now, scheduled refresh, or Refresh API) only reprocesses the data tables, field parameters are metadata/calculated table objects defined in the model schema, so they persist through normal refreshes.

Where field parameters do get affected or lost:

• Republishing the .pbix from Desktop overwrites the entire model definition, including field parameters, if the new version doesn't include them.
• Deployment pipeline promotions can overwrite field parameters if the target stage's model differs from source.
• XMLA/Tabular Editor scripted deployments will drop field parameters if they're not included in the deployed schema.
• Renaming or removing the underlying fields/measures referenced by the parameter breaks it, even though the parameter object itself still exists.

So the safe rule: scheduled/manual data refresh = safe, any full model redeployment = check first.

Hi powerbiexpert22​,

Thank you for reaching out to Microsoft Fabric Community.

Thank you ShahRukhSameer​, krishnakanth240​ , Olufemi7​ and DreamITLearn​ for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.

Thanks and regards,
Anjan Kumar Chippa

Hi powerbiexpert22​,

Just to add one small distinction to the good answers already given:

A normal semantic model refresh does not recreate the field parameter itself.

Field parameters are part of the semantic model definition, while the parameter table behaves like a calculated table. Microsoft documents that calculated tables are recalculated during refresh, so the existing parameter definition is reevaluated, but it is not rebuilt from scratch.

The main situations I would be more careful with are model redeployment or republishing, because those operations can replace model metadata, and changes to fields referenced by the parameter can also break the parameter if those dependencies no longer resolve.

So in short:

• scheduled/manual refresh -> existing field parameter remains and is recalculated
• republish/redeploy/model replacement -> check the parameter definition because model metadata may be overwritten
• If the underlying fields stay unchanged, a normal refresh should not remove or recreate the field parameter.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi powerbiexpert22​,

We wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.

Thanks and regards,
Anjan Kumar Chippa