This topic contains 7 replies, has 0 voices, and was last updated by corey 10 years, 5 months ago.

  • Author
    Posts
  • #4760 Score: 0

    nathanah
    • Contributions: 0
    • Level 1

    I just updated to version 2.3.0 of the IDE and resynced script ids but now anything that is a custom field, the intellisense is returning the internal ID of the fields instead of the name of the field. I tried resyncing but that didn’t work. Kind of disappointing that this was released with such a large bug. Anyone else running into this issue?
    This is a cached copy. Click here to see the original post.

  • #4761 Score: 0

    corey
    • Contributions: 0
    • Level 1

    RE: IDE 2.3.0 Issue – Custom fields returning ids not names

    That’s interesting. I hadn’t noticed that but it explains my post from yesterday. I had turned off validating so I could get notified of real errors. I re-synced today after turning on validation again and every custom field is underlined with a red line and if I hit ctrl+space in the quotes I get a list of numerical internal id’s. I can click on the number and get a pop up with the name. If I replace the friendly internal id with a number and rebuild the project the error goes away.

    This is not a work around. We need to be able to sync the ids correctly.

  • #4762 Score: 0

    corey
    • Contributions: 0
    • Level 1

    Oh, FYI. I not only updated my previous version of Eclipse but I downloaded the newest version and replaced the old. Both have the same behavior.

  • #4763 Score: 0

    August Li
    • Contributions: 0
    • Level 1

    We are working on fixing this bug. Sorry for the inconvenience caused.

  • #4764 Score: 0

    nathanah
    • Contributions: 0
    • Level 1

    Any timeline on when this will be resolved?

  • #4765 Score: 0

    August Li
    • Contributions: 0
    • Level 1

    it is included in the next efix, which will be tomorrow, I think

  • #4766 Score: 0

    August Li
    • Contributions: 0
    • Level 1

    fixed in 2.3.1 which has been released

  • #4767 Score: 0

    corey
    • Contributions: 0
    • Level 1

    Confirmed. It’s fixed and working. That was quick. Thanks.

You must be logged in to reply to this topic.