Indexof error

  • 1
  • Problem
  • Updated 3 years ago
  • Acknowledged
After making an upgrade to the most recent Skuid version I have a page that not longer saves.  Does anyone know what this means?  

I am using the same "Save" sequence

Has something changed in Skuid code?
Photo of Bill Fox

Bill Fox

  • 7,954 Points 5k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Ben Hubbard

Ben Hubbard, Employee

  • 12,490 Points 10k badge 2x thumb
Hi Bill,

Can you click the little arrow next to your error message in the console to reveal the rest of the stack trace and upload that picture? That will help us narrow down the issue.
Photo of Bill Fox

Bill Fox

  • 7,954 Points 5k badge 2x thumb
Photo of Ben Hubbard

Ben Hubbard, Employee

  • 12,490 Points 10k badge 2x thumb
Interesting. Are you able to grant login access to this org so I can see if I can diagnose this? Follow the instructions below and I'll take a look.
http://help.skuidify.com/m/getting-started/l/182412-getting-help-how-to-grant-skuid-login-rights-to-...
Photo of Bill Fox

Bill Fox

  • 7,954 Points 5k badge 2x thumb
I have granted you access to 00Dj0000001oO90.  I believe that it has something to do with metadata.  This started to happen after the last release upgrade.  I was able to do this before.  here is a related post: https://community.skuidify.com/skuid/topics/will-date-field-write-to-a-date-time-field?rfm=1&top...

The page to look at is R_Add_Engagement  you can enter data as it is not live yet.

(Edited)
Photo of Ben Hubbard

Ben Hubbard, Employee

  • 12,490 Points 10k badge 2x thumb
Ok, I took a look at this. This is a bug in Skuid that has to do with overriding a date/time field in the database to a date field in the UI. Although I don't think this is a regression. As far as I can tell, this particular setup has never worked. I'll put this in a bug to be fixed in a future release. Unfortunately, the fix will not make it into the upcoming "Update 7" release.