6

the industry we try to make for them their first inhouse app, is having a lot of data that we need to import to the app. (machines, workers, materials, products, etc). The problem is that they want to give them to us in excel files, instead of making data entry. So thats ok for start, but after some point of complexity and relations we figured out that it turns to be a deadend.
How do you manage situations like this, with huge old fashion companies??

Comments
  • 2
    I'm curious why this is a dead end? CSV file handling is quite a common process using ETL.
    If it's really a problem then an honest discussion as soon as possible is best way forward.
  • 0
    @dan-pud

    well yeah we convert them to csv but we mostly have problems with the consistency they write the cells
  • 1
    @dan-pud so i assumed is mostly a matter of collaborating and not a practice/technical issue right?
  • 2
    @gatoMalicioso yea that last one I think you hit it on the head. The solution is simple, tell them very firmly to evolve or die out with the rest of the dinosaurs.

    Also, your given quite a few characters when you post something. It tends to expedite things a little if you utilize as many as you can to fully elaborate on all the relevant details, such as the company not using any sort of consistency that could, at the very least, be predicted and possibly automated.

    But in any case welcome to devRant.
  • 0
    @gatoMalicioso yep
    CSV is a fairly unforgiving format. You could have validation where if not enough columns (or whatever) it kicks it out then continues processing the next row. Then you can just hand back the errors and let them sort it out for retry later. That's a common error handling pattern for a more manual approach to a batch system. More effort will be able to automate things better
Your Job Suck?
Get a Better Job
Add Comment