Comments

6 comments

Date Votes
  • Konsta Danyliuk

    Hello Ganesh.
    May I ask you to provide more details on the issue, please.

    • What Datameer version do you have?
    • What changes have been made to the Workbook or its sources before the issue emerged?
    • As far as I understand, you are getting this "Unable to coerce" error while opening the Workbook, arent you? In the screenshot, I see the errored column. Please let me know what formula do you have there.
    • What error do you see in the job.log for failed execution of this Workbook?

     

    0
    Comment actions Permalink
  • Ganesh Saptharishi
    • Version 7.5.12
    • No change.  workbooks migrated from one environment to a new environment
    • Yes, you are right.  when opening the workbook
    • no formula in the current workbook.  on exchange of data from the source sheet the error goes off
    0
    Comment actions Permalink
  • Ganesh Saptharishi

    In the previous set up many other workbooks were set to trigger on arrival of data in one workbook.  But I now notice that all the dependent workbooks show a similar error and calls for manual exchange of data.  can this be avoided?

     

    0
    Comment actions Permalink
  • Konsta Danyliuk

    Hello Ganesh.

    • May I ask you to explain how exactly have you migrated the Workbooks from one environment to a new environment, please.
    • Are both Datameer instances have the same version? 
    • Any changes in Workbooks' sources between environments, e.g., columns data types?

    >on exchange of data from the source sheet the error goes off

    What exactly do you mean by this? Could you provide more details, please

    Thank you.

    0
    Comment actions Permalink
  • Ganesh Saptharishi

    Thanks for your response.

    • Since I am not an admin, i am not clear on how the migration is done.  all the workbooks from the previous environment is copied as is is my understanding
    • yes
    • No changes in sources or datatypes
    • we had a back up of workbooks copied from previous environment and I could open without any issues.  On the workbook i was working, initiated an exchange of data and selected the source from back up workbook.  Then I noticed that the error on the columns vanished.  
    0
    Comment actions Permalink
  • Alan

    Hi Ganesh,

    I was looking at the error message and the value:

    2095.757640000000000000 mentioned is too long to fit as a double.  With the decimal this value is 23 characters long, or 22 digits.  A Java double stores 8 bytes, so can hold up to 15 digits.

    There has been a change in the data as the root cause of this problem, and the error message is correct. The easiest way by far to get this addressed will be to work with the source data administrators and have the column fixed, then no changes in Datameer will be necessary.

    If they cannot fix the issue, you will need to create a workbook to fix the column based on whatever data type it has, to make it consumable as a double, then exchange the first source sheet in these workbooks.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post