You’re offline. This is a read only version of the page.
Right, I'll do my best here, but I don't understand what or why this is even a problem, and it's frustrating me somewhat.
We have taken over support for an older CRM 2011 system - a lot of work happened before we took it on and it's pretty difficult to understand whether this is something we've accidentally broken or otherwise.
On making a few field updates and customisations to fields within the main view of their opportunities, it has somehow been "messed up". I say this, as I can't actually see how it's "working" in the first place.
Both Dev and Live look identical from a design perspective (I've blanked a couple of descriptions for security purposes):
This "tab" seems to be marked as showing, but it doesn't - at least not on live anyway. Here is what the live / dev system looks like:
DEV (correct):
LIVE (incorrect):
Note the red ring - in the case of Dev, it shows an entire section that apparently doesn't exist in the view when designing it. I thought at first it was this "Tab" that you see in the first picture, but the fields it shows are different to what it contains, plus the "expand this tab by default", "visible by default" and all sorts of other things are IDENTICAL to dev and live.
I'm honestly out of ideas of what it could be. I thought it might be some javascript running onload of the form to show, but I've checked and again both dev and live are identical.
It makes no sense to me? Any help would be appreciated.
Craig
*This post is locked for comments
I have the same question (0)
Bizarrely, I think I've managed to fix this by "breaking" it on Dev, not that it made any sense - the tab called "tab" didn't have the label showing, nor was it set to expand by default, yet it was doing it on live and on dev. I went in and showed the label, to confirm it was indeed this "tab" and it appeared, but as soon as I turned off the label it vanished completely in the same way live did.
So I gave it a proper name, told it to expand by default and it's now working on both dev and live...
Doesn't explain why it was working before though?
Share
Report
All responses (
Answers (
4
