Details about this thread
  • State Not Answered
  • Replies 4 replies
  • Subscribers 312 subscribers
  • Views 1027 views
  • Users 0 members are here
Related content from around SugarClub

Dropdown back-end not matching front-end

Josh Wright

Hello all,

I have a strange issue I have never encountered before and cannot seem to figure it out.

I have a module called "opportunities" with a custom field called "Sales Type". Within this field is a dropDown. However, the dropDown on the back end in studio does not match the values stored in the front end. I am making this to try and figure out a solution without deleting the current values stored in this field. I will attach pictures of the vardefs and the discrepancies.

Front end: 

This is a really strange issue and I would like to figure it out for future reference.

Thank you.

Parents Reply Children
  • 0 in reply to Hatim Alam

    Hello hats,

    The user and group are configured correctly. I am on site. I went ahead and deleted the cache folder and rebuilt and no change. It still has Elastic_boost_options. This is the only time I have ever seen this which is why I asked. I may just need to make a new field and move everything from the old field over, but I had wanted to avoid doing that if possible in order to try and figure out the actual cause. I have quick repaired multiple times. "Second Appointment" does not match the front end, as I stated above, so that is not the correct drop down. There's something wonky going on.

  • 0 in reply to Hatim Alam

    I went ahead and changed the drop-down field and lost the data contained within, but at least I can add fields and such to it. As such the issue is resolved... but the outstanding issue still exists on our test copy if anyone has any other ideas on cracking it, for my future reference.