I recently completed the Development on Creatio guided learning course. With my instructor's assistance, I set up a local Creatio instance—labeled Dev1_DEV—on my Windows server.
 

After switching my D1_DEV local development environment to use File System Development Mode instead of the default Creatio IDE mode, I encountered an issue where my Creatio instance failed to load the necessary JS files related to SectionModuleV2 for Classic UI sections (e.g., System Settings, Lookups). I reverted my Web.Config file changes to disable File System Development Mode, which resolved the issue.
 

For reference, I have attached screenshots of the error messages from my console when attempting to access Classic UI sections while File System Development Mode was enabled.
 

Could you help me understand why switching to File System Development Mode prevents access to the required JS files for Classic UI sections? Aside from modifying the Web.Config file, I did not make any other changes to the system. 

Any guidance on resolving this would be greatly appreciated.

Like 0

Like

7 comments

Hello,

 

We recommend checking if all the steps from the article have been completed:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

 

For example, ensure that these values are set:

<fileDesignMode enabled="true"/>
...
<add key="UseStaticFileContent" value="false"/>


All steps must be completed.

Hello Kalymbet,
Hope all is well. 

Thank you for providing that link. I followed its steps listed on the page as follows: 
Enabled file design mode
Disabled UseStaticFileContent 
Compiled my instance (no errors)
Downloaded packages to file system successfully (no errors)
Gave IIS Usr full access to the Terrasoft.Configuration file

I still received the same error. It looks like it is not able to find the SectionModuleV2.js file. 




 

Kalymbet Anastasia,

 

Hello,
 

We also recommend that the user under which the application pool is running should also have full access to the {rootAppFolder}\Terrasoft.WebApp folder

Folder access

Serhii Parfentiev,

Thank you for the suggestion. I added Full control access to the IIS User for the Terrasoft.WebApp folder and I still received the same issue. For reference, I attached an image of the Terrasoft.WebApp security properties. 

 

Hello,
Could you please verify under which user the Application Pool is running? If you have changed the user, please make sure to grant permissions for this user too.

If this doesn't help, additionally please try the following scenario:
1) Deploy the application.
2) Authorize and allow the inner part of the application to initialize (after login, wait for the application to finish loading).
3) Only after that, make changes in the Web.config file to enable development on the file system and follow further instructions. 

Show all comments

Hey. I've been working with Creatio for some time already. And I've been facing an issue. The issue is not picking up on changes that were added to the files already added to the package when uploading a new version of a package on any environment. I am talking about .cs files, in other words, the source code type of Creatio files. So, when I finish fixing some bugs with the package locally, I go to the dev env. to upload the package there. I do the uploading via `ApplicationHub` page via `install from file`. So, the issue happens only when the previous package version is installed and I want to update with the newer version. If I remove the previous version and upload a new one, all new changes are picked up.

Like 0

Like

1 comments

Hello!

 

In this case, it could be two possible options as to why it happens:

 

1. It can happen if the schema has a more fresh ModifiedOn date in configuration, for example, if it was recently modified directly on the environment; if so, the schema won't be updated.

2.  Sometimes, the schema updates only after full compilation. so the steps will be install package -> full compilation -> check the schema.

 

If the issue would still reproduce, contact us at support@creatio.com.

Show all comments

Hi All,

 

I am facing an issue with the file system development mode. I was trying to enable file system development mode on my local setup for a package that I developed on a cloud setup. When I installed the package on my local setup and compiled, there was no error. But after enabling the "File System mode", then downloading the package to the file system, when I tried to compile I received many errors w.r.to the js files in the package. But everything is working as expected on the UI. Screenshot attached for reference.

 

Local setup Version- 7.18.4

Cloud version-7.18.3

Like 0

Like

5 comments

Hi,

 

Please provide the code inside the file that returns an error.

Hi Oscar Dylan,

 

The error is showing for all the available schemas in the package, but inside the schema there is no error. I have attached one sample schema where error is showing.

 

 

 

Sourav Kumar Samal,

 

it's strange that these errors are returned for .js files upon compilation that should affect only C# schemas. Try generating the source code for all items and then compiling once again.

Hi Oscar Dylan,

 

Yes I have tried that also but the error is still showing. The error is showing only after enabling the file system mode and downloading the package to the file system. But before that there was no error showing.

Sourav Kumar Samal,

 

Got it. Please email us at support@creatio.com, provide us with the package that was installed and with a description on how we can reproduce this issue using the clean OOB version of the app. We will try to reproduce the issue on our end.

Show all comments

Hi team,

Many times we encounter the error as seen in the below image: 



The above errors are encountered while building workspace in visual studio and also while installing packages. These 'duplications' seems to be coming from auto-generated files.

 

We have followed the instructions to set up file system development mode as per the documentation. Could you please let us know how to overcome this issue?

 

Thanks

Like 0

Like

2 comments

Hello Shivani,

Unfortunately, the image is corrupted and cannot be opened. Could you please resend it?

Thank you in advance!
Olga.

Hi Olga,

I am reattaching the same image 

Show all comments