This change to credits based billing is causing significant pain for our business.
It is ridiculous that each record in a data store costs 1 credit when it is counted.
We have datastores with sometimes 100+ records in them which we need to count to determine the router outcome, and these scenarios literally cost 100x more now.
We are going to need to migrate to another service because of this.
Welcome to the Make Community, Benjamin_Rodgers!
I am not seeing this issue in both the Data Store’s Search or Count modules, and they both only use a single credit as expected.
A common mistake that is made, is that multiple bundles from a previous module has not been aggregated into a single bundle. This makes modules after that run once PER bundle.
Every result (item/record) from some modules (like trigger/iterator/list/search/match) will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, you’ll need to use an aggregator of some sort.
Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and can apply to many use-cases like building of JSON, CSV, HTML.
You can find out more about the other types of aggregator modules here:
Question: Which is the best aggregator do you think you’ll need for your use-case?
Here is an example of how your scenario could look like:
This is just an example. Your final solution may or may not look like this depending on your requirements and actual data.
For more information, see “Mapping with arrays” in the Help Centre. You should also do the Make Academy, which also covers the use of Iterators & Aggregators.
I hope this information assists you. If you are still having trouble, please provide more details in a new thread.
— @samliew
Hi Benjamin, as Sam Liew also mentioned – I can confirm that nothing has changed in terms of how much costs are associated with interacting with Data Stores. Previously it was one operation and now it is one credit. Same exact costs. See Sam’s post for a detailed example of how to deal with aggregations to ensure things are cost effective.
Agree! 10 lines of a spreadsheet counts as 10 credits is so expensive and then you need to do some tools actions which also 10 credits to substring or something… it just spent all my credits in 1 run! 
@Make @Misha-Inactive
Welcome to the Make community!
As stated above, nothing has changed. Sometimes, you’ll just need to utilise tricks to reduce the number of operations, and the most common one is to aggregate all the bundles first to process them in a single operation.
I’d recommend going through the Make Academy if you haven’t yet!
Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —
parseDate | tokens for formatDateHope this helps! If you are still having trouble, please start a new thread.
— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!