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.
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.
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.
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.
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.
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.
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.
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?
