PR: Adding IFC Shared Parameters-RevitIFCBuiltIn-Type to Parameter Service

[PeterTranberg]

Problem Description

... It seems that the IFC Shared Parameters-RevitIFCBuiltIn-Type_ALL.txt are not able to be loaded into the ACC Parameter Service. Is this adressed to the ACC team or is it an issue that will be fixed in the Shared Parameter File. I see that it has been reported to Autodesk https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Parameters-Service-rejects-IFC-type-parameters-due-to-square-brackets-in-Revit.html but maybe som of you in here have more information. The issue is [] which is on the Parameter name limitation list here https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/3RVyShGL7OMlDJPLasuKFL.html

Revit Version

2026.4.x

IFC for Revit Addon Version

26.4.1

Windows Version

11 25H2

[ArtemHnatko]

Hello @PeterTranberg,

Thank you for bringing this to our attention and providing the detailed links.

Previously, as discussed in issue #558 , these characters were permitted because local Revit versions could process them via API or text files. However, we recognize that the Parameters Service enforces stricter naming rules aligned with modern web and database standards. This has turned what was once a "by design" naming choice into a functional blocker for cloud-based workflows.

This issue is also reported in Jira as "REVIT-249214" and is currently in the "Open" status.

[AngelVelezSosa]

Actually, I believe this is something for the Parameters Service. These parameters have been out for some time, and many people use this pattern.

[PeterTranberg]

Actually, I believe this is something for the Parameters Service. These parameters have been out for some time, and many people use this pattern.

Thanks @AngelVelezSosa I agree, is the IFC team pushing to get this fixed by Parameter Service team? I see that @ArtemHnatko mentions a Jira report as open, but maybe it is time for escalation.

[AngelVelezSosa]

Perhaps re-escalation is the better term here :) I'll check in on this.