0.18.1

Reading a connector's records

When you ask for a list, a sort, a filter or a total, FloConnector puts the records in a temporary, in-memory analytics workspace and answers the question there. For some connectors the records were arriving wrapped as one item instead of as individual rows, so questions like "sort these by search volume" or "how many are there" could fail, or come back empty, even though the connector had returned the data.

Those records now arrive as rows. This was most visible on DataForSEO, where it affected every tool, but the fix is not specific to that connector.

Matching records across connectors

Identifier fields now keep a consistent type when a connector leaves them blank. Before this, a single blank ID could change how an entire column was read, so matching jobs to clients, or records from one connector to another, could work in one conversation and fail in the next with a conversion error. It now behaves the same way every time.