Whose sockie is MF, no one really experiences this much fail surely
-
Doing the needful since 1827 -
Sack Test Monkey who signed off the Exit ReportOriginally posted by mudskipper View Post
Sack Release Monkey who failed to do due diligence
Sack Change Monkey who failed interrogate the work of the aboveOriginally posted by Stevie Wonder BoyComment
-
But first sack the product owner who didn't check what any of the, was signing offOriginally posted by SimonMac View Post
Eek in its just MF's attempt to escape now rather than later modemerely at clientco for the entertainmentComment
-
Is it salesforce?Originally posted by minestrone View Postmerely at clientco for the entertainmentComment
-
I wish I could publish the email trail I have, it's absolutely fantastic. They've now found the route cause and it's classic schoolboy error.
It starts with a screenshot of my comments on the original story saying 'NB. Check the label / field change does not cause an integration problem'
Then a number 'about 20' emails back and forth with an ever increasing number of people (now 20) chipping in, pointing out a possible solution.
Eventually it was found that on system A as well as renaming the labels they made the column name similar, do similar the integration code picked up the new field name instead of the other. Of course after lots of finger pointing and an ever increasing number of 'I disagree with the last email' they've now come to the conclusion it was nobodies fault and a problem with the platform. The solution to add -new- in the name of the new field as opposed to making it identical to the old one.
FFS this is route 1 schoolboy error. Makes me laugh though.
What happens in General, stays in General.You know what they say about assumptions!Comment
-
what they couldn't speill? Its Roots of a tree!Originally posted by MarillionFan View Post
well at least you come out smelling of roses. Well done, always send the CYA mail eh?Always forgive your enemies; nothing annoys them so much.Comment
Comment