Jacob

My feedback

  1. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Caspio Bridge  ·  Flag idea as inappropriate…  ·  Admin →
    Jacob supported this idea  · 
    An error occurred while saving the comment
    Jacob commented  · 

    I totally agree. Some of my tasks error out due to the limitation and I have to mosify them and do one by one while modifying.

  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Caspio Bridge » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Jacob shared this idea  · 
  3. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Caspio Bridge  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jacob commented  · 

    Yes, this would be great if the error detail would say which row had the error. Sometimes I import a file with 9000 records and I might have one record fail and then I have to figure it out. This would save me hours in work because on some of my imports, I have to enter certain information in the file first before i know if there was an error I wouldnt know which row so I put a unique value manually on everything so I dont get any errors. Very time consuming

    Jacob supported this idea  · 
    An error occurred while saving the comment
    Jacob commented  · 

    Much of our data is imported into the database with a CSV file. Some files can have 9000 rows.
    It is very important for me and I am sure for others to have more details given about an error during import. Even a debug page that someone could look at and decipher what went wrong.

Feedback and Knowledge Base