Taylor Downs

Jobs are business processes turned into functional-style scripts. What does that mean, how should you approach writing jobs?

This is a quick one, but I just got off an exciting call with an organization that's going to set up some jobs to move data into Salesforce from CommCare and realized that despite this being one of our more common integration requirements, we haven't done a 'tips' article for this type of project. Until now.

tl;dr: Lots of our users want to upsert tracked entity instances in dhis2, but upserts aren’t supported by a standard DHIS2 API endpoint. We built one in our dhis2 adaptor: it’s composed of existing APIs and a bit of logic 🤔. Now you can upsert tracked entity instances to DHIS2 👍 ✅.

Hi all, this is a quick one from the product team at OpenFn — we've made a major upgrade to how timed/period jobs work.

Hi all, this is a very short post with a simple message: design for failure. Even if you've never heard of MSSQL (or Azure, or Microsoft?), I want to talk for one moment about the importance of upserts and a funny developer term called "idempotence."

Does your organization's information have an underlying structure? Try this exercise using boxes and crow's feet.​

This article was originally posted by Taylor Downs, Head of Product, on The OpenFn Founder's blog as "The power of crow's feet."

It’s Saturday Morning in Cape Town and I’ve just spent an hour talking about how a non-profit is organized. I thought I was getting into a technical discussion—I’ve been doing system architecture discussions for years—but what we ended up talking about was how this NGO thinks.