LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  .xls formula issue

    Employee
    Posted 09-30-2015 07:27

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

    Originally posted by: dtigue

    Hi,

    I have seen an issue with the Excel File node when used with .xls files rather than .xlsx.
    If the .xls file contains formulas relating to text transformation, e.g. TRIM, LEFT, MID, etc then the Excel File node will convert this field, and the remaining row to NULL.
    It then appears to put a NULL row underneath this record.
    This does not appear to happen when using other types of formula, e.g. maths formulas such as AVG, MAX, SIN, etc.
    This also does not appear to happen when using .xlsx files.
    I have included (below) a table for others to test this (can't seem to upload Excel file as attachment) - copy the table below and paste to excel (is pipe delimited so will need to seperate out using text to columns), saving as .xls, and then attempt to open with the Excel File node.
    Just wondering if there is a setting within the Excel File node that I should be using or if this is a genuine bug?

    Thanks

    Danny

    A|B|C|D|E
    1|=TRIM(A2)|A|bcd|34
    2|=TRIM(A3)|B|fgd|35
    3|=TRIM(A4)|C|bcd|36
    4|=TRIM(A5)|A|fgd|37
    5|=TRIM(A6)|B|bcd|38
    6|=TRIM(A7)|C|fgd|39
    7|=TRIM(A8)|A|bcd|40
    8|=TRIM(A9)|B|fgd|41
    9|=TRIM(A10)|C|bcd|42
    10|=TRIM(A11)|A|fgd|43


  • 2.  RE: .xls formula issue

    Employee
    Posted 11-09-2015 03:32

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

    Originally posted by: dtigue

    Has anybody been able to try this to see if they get the same results?

    Thanks

    Danny


  • 3.  RE: .xls formula issue

    Employee
    Posted 11-10-2015 06:36

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

    Originally posted by: lnason

    I was able to recreate the issue you describe above. This looks like a bug and so I've opened a support request. (CS-11459)