Hi René,
To make the model images and reports available, you must add these files to the Web GUI files before deploying it to Azure, for example in a
model subfolder.
Then you will need to update the (absolute) path in the model to a relative path, using the
Relink files task in IAM.
We know this is somewhat cumbersome and are working on a feature to include all model files in the metamodel database. We expect to deliver this feature with the 2020.1 release in January.
Unfortunately using a relative path doesn't work. Tried this both on the Azure environment and on a local IIS environment.
I've also tried this on a test project started with SF in stead of IAM, setting the path relative with no result.
This is the dummy task I use:
This is the content of the folder (sandbox is the web gui folder):
If I specify the full path to the IIS folder:
C:\inetpub\wwwroot\sandbox\model\task_generic_add.png
as icon in stead of:
.\model\task_generic_add.png
, it does work.
Are you sure the .\ relative path is allowed to use? Or is the relative path not based on the root folder of the web gui?
Hi René,
I have some additions to the post above of Jasper.
Hi René,
To make the model images and reports available, you must add these files to the Web GUI files before deploying it to Azure, for example in a model subfolder.
Then you will need to update the (absolute) path in the model to a relative path, using the Relink files task in IAM.
We know this is somewhat cumbersome and are working on a feature to include all model files in the metamodel database. We expect to deliver this feature with the 2020.1 release in January.
Please replace the directory with resources to the 'App_LocalResources' directory. A web-server like IIS or a Web app in Azure does not allow the web application to read files from the deployment directory accept some marked directory, like the one above.
The specified path in the SF is fine this way. Maybe you should even remove the './' in front.
Kind regards,
Erik
Hi René,
I have some additions to the post above of Jasper.
Hi René,
To make the model images and reports available, you must add these files to the Web GUI files before deploying it to Azure, for example in a model subfolder.
Then you will need to update the (absolute) path in the model to a relative path, using the Relink files task in IAM.
We know this is somewhat cumbersome and are working on a feature to include all model files in the metamodel database. We expect to deliver this feature with the 2020.1 release in January.
Please replace the directory with resources to the 'App_LocalResources' directory. A web-server like IIS or a Web app in Azure does not allow the web application to read files from the deployment directory accept some marked directory, like the one above.
The specified path in the SF is fine this way. Maybe you should even remove the './' in front.
Kind regards,
Erik
Thanks, that works.
I've moved the folder 'model' from the example I've given above to App_LocalResources, changed the path's to "model" ( in stead of ".\model"), that works both on a local IIS and an Azure App Service.
