Having support for display folders is critical in large models and should be a native feature to support a formal build process. Using the BIDS Helper third-party tool to add folders works when manually deploying a model from the development environment but does not address scripted and automated deployment scenarios.
In our daily build cycle, every application component in our solution is built and deployed directly from checked-in TFS projects. When the tabular model is deployed from the latest .asdatabase file using XLMA script, it does not include display folder definitions. This requires the deployment administrator to make an exception by opening the project in Visual Studio/SSDT and then manually deploying to a temporary location to invoke BIDS Helper. The deployed database is then scripted and added to the solution build for packaged deployment.
Deployment automation is important. Our solution is a large multi-tenant web application with integrated analytics and reporting. We make frequent changes to the model definition which is replicated to many AS databases. The model contains hundreds of measures so display folders are needed to provide a good user experience.