Error with Custom Fields

We just started using Insightly, and I have started to create some custom fields, and testing them. I am getting what looks to be an HTML error when I use them in the Organizations (only place I'm testing so far) area. This pertains to Dropdown Fields only so far: when I create one, it works fine, however when you go to edit the field inline, I get this flashed to me:

 

It only happens when you edit the field when you're editing a record. When you edit the field when creating a new Organization, it seems to be okay, but after you save it, and try to edit again, it does this.

Please help.

Thanks!

0

Comments

13 comments
  • Hello Justin, thank you for letting us know! 

    Just to clarify, when you say "editing the field" do you mean clicking on the drop down and choosing a selection? 

    Also, have you tried testing this on any other browsers? And is it still happening? 

    I was unable to reproduce this using Chrome, so any Insight would be great! 

    Thank you!

    0
    Comment actions Permalink
  • Hi Jessica,

    Thanks. Yes, that's correct. When you choose a selection in the dropdown, this error pops up immediately when you make the selection. I am also using Chrome, up-to-date.

    I just tried in Firefox and am not getting the same result, it works fine. I will try clearing browser cache and see if that helps in Chrome.

    Thanks.

    0
    Comment actions Permalink
  • @Justin - Thank you for letting me know! I await the results of your cache clearing!

    0
    Comment actions Permalink
  • Jessica,

    This seems to be an error with inline editing only, when a custom field is not already pre-populated when you create the record, or when you use the full-edit function.

    For instance, I created an Organization, filled in 3 of the 5 custom fields I created, saved it, then went to the Organization page, attempted to edit the non-pre-populated fields inline, and the error then flags. This no longer just applies to dropdowns either, as I tried it with text-fields and got the same result.. This is cross-browser.

    0
    Comment actions Permalink
  • Well, now I'm not getting it anymore. Odd, very odd. Oh well, as long as it's resolved, that's good with me! 

    0
    Comment actions Permalink
  • @Justin - Well, hopefully it should stick! Let us know if it comes back and we can dig into it. 

    Thank you for keeping us updated!

    0
    Comment actions Permalink
  • Justin,  any idea how you fixed your error?  We are having the same issue, using Chrome browser and custom fields.  You can enter characters in the field, but when you click the save (checkmark) button, the error pops up.

     

    Thanks,

    0
    Comment actions Permalink
  • Hi Tara,

    We are still getting the error on our end, albeit erratic and not consistent. One of our Salespeople said he gets it sometimes, and then other times he doesn't - when editing those custom fields inline.

    The custom fields are still the only ones that pop the error off, and only while editing inline when not previously pre-populated. I know this has become a little bit of a nuisance to one of our Salespeople who told me it's much easier edit inline then go in to 'full edit' if the Organization is already created, and he wants to enter info in real-time when on the line with a prospect. It just reduces one step. Think it's still worth looking in to on Insightly's end.

    Hope this helps.

    0
    Comment actions Permalink
  • @Tara & @Justin - We thought we had this fixed but it appears to be cropping up again. 

    I'm going to forward this on to our engineering team so they can take a look into it. 

    Once I have any updates, I will notify this thread!

    Thank you!

    0
    Comment actions Permalink
  • @Justin - Thank you for your patience with this issue!

    Great news! The bug has been fixed and the update was pushed out so everything should be working now. 

    Please let me know if you run into any issues with this!

    Have a great day!

    0
    Comment actions Permalink
  • Hi Jessica,

    I have the same issue with custom fields for Organizations and Contacts. If information is added in full edit mode, the information stays. Inline editing works if information is added to a field with existing data (added in full editing mode). If no data has been entered, information added in inline editing mode disappears,

    Same issue for both Chrome and Explorer.

    I have an open TR 116792 since December 12 on this issue.

    0
    Comment actions Permalink
  • @Ola - Thank you for checking in! I am aware of your ticket as well, we had another issue crop up after the fix went out that we're still investigating. Since you already have a ticket, we will update you there as soon as we have any information or resolution. 

    There won't be any releases until after the start of 2016 so we will notify you as soon as a fix is released. 

    Thank you! 

    0
    Comment actions Permalink
  • Hi everyone:

    We've heard back from our product teams that the inline editing has been resolved. If you are seeing otherwise, please let us know.

    0
    Comment actions Permalink

Please sign in to leave a comment.