LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Pedro Pablo

Hi,

I have a problem in a real use case when I read a excel and then write into a new excel that is used in next day execution as input (and in the middle exists the posibility someone open and modify some value)

I explain the steps:
Step 1)
In BRE I see 1500.50, then I write into a Excel File using 'Excel Node' and finally I open using Microsoft Excel, I see 1500,50 so all is ok because it is the correct system locale (Spain).
Step 2)
I read the file using a 'Excel File Node', I read 150050 without comma or period, it is wrong!!
If I use the option UseSystemLocale in 'Excel File Node', I read 1500.50
Step 3)
Someone opens the file with Microsoft Excel, makes a change and saves it, or does nothing and simply click on save
Step 4)
I read the file using a 'Excel File Node', I read 1500.50
If I use the option UseSystemLocale in 'Excel File Node', I read 1500,50


I need a solution that works reading a file generated from Microsoft Excel as well as generated from BRE and works too with my sytem locale region (decimal dot and thousand comma separated) .

It is a real use case.
Thanks.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi Pedro,

Would you be able to provide examples of the files used as input to Step 2, Step 3 (unchanged and changed) and Step 4?

Can you also provide details of which version of Lavastorm you are using (6.1.1/6.1/6.0) and the platform (Windows/Linux). It would also be useful to know which version of LAL you have installed onto your base Lavastorm installation.

Many thanks,
Adrian

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Pedro Pablo

Hi,

I attach Excel files, the original and the generated excel. And screenshot of all obtained

My BRE version is v6.1.1.0 Build 47 Windows platform
Attachments:
files.zip

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi Pedro,

Unfortunately, I am unable to replicate the issue shown in the '4-read excel generated by BRG.png' image so I will pass this issue to Support.
Re. the version of Lavastorm you are using I do not recognize build 47 - the current GA build for v.6.1.1.0 is build 51, which is available
from the following link on our website: http://www.lavastorm.com/lavastorm-installers/

Update: We are launching a new version of our website today and the above link is currently not available in the new site.
The lavastorm installers repository can be located by either typing "Lavastorm Installers" into Google or going to the relevant
Salesforce page directly:

http://na3.salesforce.com/_ui/selfse...0150000000s09A

As an interim work-around, would it be possible for you to use a delimited file as the intermediate file format (as a replacement for 'file2.xlsx')?
If the results are saved as a semi-colon ( ; ) separated file with a .csv suffix then the file would open in Excel for other users for their review.
Should the user want to change values in the file they could update the fields and save it (retaining the .csv format).
The dataflow could be updated as shown in the attached example to import the .csv file and optionally replace any comma decimal point characters
with a period character in the appropriate fields (using the Replace Text node).

Regards,
Adrian

Excel Problem_Alternative.brg

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Pedro Pablo

Hi Adrian

The problem does not happen on Server ( buildVersion:6.1.1.0.51 Team Plus Edition )
But it happens running on local server with last version of LAE and Libraries:
Lavastorm_Analytics_Engine6_1_1_0_51-Desktop-windows-x86-32
Lavastorm_Analytics_Library_Pack-6_1_44_0_29-windows-x86-32

it's curious, when I run on Enterprise Server I get:
Step1 (read original file): 1500.34 (UseSystemLocale = false) and 1,500.34 (UseSystemLocale = true)
Step2 (read generated file in BRE): the same result
Step3 (open and save from MicrosoftExcel and read from BRE): the same result
While on Local Desktop Server:
Step1: 1500.34 (UseSystemLocale = false) and 1.500,34 (UseSystemLocale = true)
Setp2: 150034 (UseSystemLocale = false) and 1500.34 (UseSystemLocale = true)
Setp3: 1500.34 (UseSystemLocale = false) and 1500.34 (UseSystemLocale = true)

Looking at the bold numbers you can notice that there is some configuration on the enterprise server in UK mode so unlike the local server that appears to be in Spanish mode.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: awilliams1024

Hi Pedro,

As another line of enquiry, I was wondering whether it would be possible to use some new functionality in the Excel File node (that was enhanced in LAL 6.1.45.0 / LAL 6.0.45.0) to solve your issue.

The Excel File node now provides a new property called "IgnoreCellFormatting" on the Optional tab which enables the node to import the underlying cell value rather than the displayed value in numeric fields.
This is typically used to acquire, say, the underlying value instead of a value that has been rounded to fewer decimal places. I don't know whether this overrides the locale-based value but it may help.