11
Tamrael
2y

Things that make you regret you are not a normal grunt in any other fucking job outside of software development...

Few years back we had the biggest customer ever close to signing contact with us (b2b). They had a CRM they wanted to connect to our CRM because their users didn't want to use IE with ActiveX anymore, the old software was a fucking RDP over IE to a server behind a VPN.

Boss brags how we can implement every API on Earth with our team and gets the contract signed. Technically not a lie but we agreed on a company meeting a few month prior to not implement each API for every customer but expose one ourselves because we had enough big customers on that one software to not want 100+ unique API connectors in our code.

So we apparently agreed to not only build our side of the API but also pay 2/3 of the bill of the other company for implement their shitty excuse of an API...

Fast forward a few month, talking to the other companies dev daily to get their API up and running, our part is long done. Finally get things set up and data flows... suddenly shit hits the fan. That shitty excuse of CRM can't expose the created and modified timestamps to the API. Webhooks never got implement and now we have no way of knowing which data changed because their side is completely passive.

Fast forward to a few weeks back. Still no solution. Shit is running, barely. Data inconsistency is low because everyone knows they should never change things in the old CRM because the changes might not be synced. (Only one indictor is a custom modified date on the main customer data that only updates if the main data was changed but there are 20+ different possible subsets. Can't get changes in subsets detected, like ever)

One fucking grunt updated 129 customer-profiles in the old CRM. Nothing was synced.

They still use the old shit for billing.

Their it-crowd-guy calls me up:
"Sorry but we need to generate the bills tomorrow and there seems to be some kind of desynchronization between the databases"

No shit? Someone did exactly what we told you not to do and now that one thing we warned you about happened but now it's our fault? Use the fucking force sync button we built for that purpose and that purpose alone. It will only take 7 days because that fucking SOAP API is slow as fuck and you have millions of datasets to sync...

Fml I might just try and jump out the window, sounds like a lot of fun in days like this.

tl;dr never implant against dynamics ax aif soap API if you want to keep some basic level of sanity

Comments
  • 2
    That's a bad position to be in. Awesome rant though. Just glad I'm not in your situation.

    Sound like there is a lot of rebuilding and coding to be done on the other side. Hope they fire the shitty programmers.

    Good luck. Hope your situation gets resolved.
  • 0
    @Jackeast as most of the shit is hardwired into the software from Microsoft (not exposimg created/modified timestamps to the API) there isn't much to do. Webhooks would costs at least a 5 figure number to implement on their side (Microsoft certified partner) and neither the customer nor my boss wants to pay another dime to that company.

    The only thing to do is not inserting anything into the old CRM. Just insert it in the new one (our software) as we always sync the data immediately to the old system with data sanity checks. I just hope the learned their lesson...
Add Comment