Hey JsForum team,

we realized the following issue using jsrReport 4.6.0. Before this version the following snippet was working in our templates to translate months to the corresponding month names e.g. to english

Before this was working before jsReport 4.0.6

{{lookup localize "months" (localizationFolder) settlementMonth}}

our current new fix is the following

{{localize (concat "months." settlementMonth) (localizationFolder)}}

Now the question: Is this the correct way to extract the data and make the translation or can you provide the correct way?

Thank you upfront

Hi @jan_blaha,

I can verify that the import in version 3.0.1 is way faster. The other good thing is also that is visible now in the logs when the import starts and when it is finished. We are thinking about an upgrade. Congratulations on the new version.

Unfortunately, we also tried the import of our templates on the new version 3.0.1 but with the same issues.

Dear @jan_blaha,

unfortunately, we still have the issue that we can not reliably work with jsReport because after re-starts of jsReport the imported files disappear from the Application and we can not generate files.

Is there a way how I can send you our sample export files in different versions so you can take a look at why it is it not working?

We already tried a look at different things, like importing in different jsReport versions etc.

Also your provided sample was working on our side without an issue. But as far as I can see your sample is around 103 kb in size and our samples are already around 600 to 700 kb in size.

Mr. Blaha,

do you have an import/export file you could send me which was working for you so I can try it out with another data sample on our environment? So I can also verify your outcome.

Importing partially (less data) from one instance to another in our environment leads to more correct behaviour. This means the data is imported and the ~.tran folder is deleted afterwards. But this is not our normal use case. Usually, we simply want to merge the data from e.g. Staging to Production.

Hi Mr. @jan_blaha,

did you also tried a merge import after a full import? In this case it is super often the case that although the import is done (regarding the logs) the ~.tran file is still there and not deleted.

Hello dear jsReport team,

currently we are using jsReport in the version 2.11.0 with:

jsreport-fs-store-aws-s3-persistence@1.4.1 (with the fix for umlauts and non ascii file/folder names)
jsreport-fs-store-aws-sns-sync@1.2.1 

After/during the import a ~.tran/ folder is created

After a while, under 1 Minute all the needed files are displayed in the GUI and can be used. As soon as jsReport is restarted e.g. the next day all the files which are in the .~tran folder are not visible or accessible anymore via the GUI.

Also it seems that the synchronization of the import takes too long to respond in the GUI although the file itself is only around 600kb in size.

Can you give me advice on how to improve the speed of the import of the zip file or is this a knonw issue that it takes too long using AWS S3 for importing files?

I tried the same thing to export and import the current templates without AWS S3 and this actions takes only seconds. With AWS S3 it takes around 3 minutes.

Hi @jan_blaha ,

I tried to find a way to solve or overcome my issue and maybe this is interesting to share with others

FROM jsreport/jsreport:2.11.0
COPY jsreport.config.json jsreport.config.json
RUN mkdir /app/.npm-global
RUN npm install \
jsreport-fs-store-aws-s3-persistence@1.4.1 \
jsreport-fs-store-aws-sns-sync@1.2.1 \
--cache /app/.npm-global
RUN chmod +x /app/run.sh
EXPOSE 5488
CMD /app/run.sh

Fist step is to create a npm cache folder where the jsReport user in the Docker file has acces to write

RUN mkdir /app/.npm-global

And in the second step to re-use this folder via npm

RUN npm install \
jsreport-fs-store-aws-s3-persistence@1.4.1 \
jsreport-fs-store-aws-sns-sync@1.2.1 \
--cache /app/.npm-global

I hope this helps some using Kubernetes and creating the image via Kaniko

Hi @jan_blaha ,

to give you further feedback on this topic.

Your provided solution works now for the full and non full version of jsReport in Kubernetes. Thank you very much for this hint:

extensions_fsStoreAwsS3Persistence_bucket

Maybe it is only a Kubernetes issue but

extensions_fs-store-aws-s3-persistence_bucket

only works for the non full version of jsReport. The full jsReport versions are not respecting the environment variable.

Thank your for your hint

Hi @jan_blaha,

to share my experience with the new version of jsreport-fs-store-aws-s3-persistence@1.4.1 it looks like that creating e.g. folders with umlauts and/or UTF-8 characters works like a charm now.

Thank you for this fast fix

Hi @jan_blaha ,

thanks for the fast answer.

I tried both in our Kubernetes environment passing the environment variables using . and _ as separators with jsReport 2.6.1 (non full version) and this is working.

But with the full versions greater than 2.6.1 (full version) both separator versions, unfortunately, are not respected although they were passed and visible in Kubernetes.