# Make advanced Data stores and structure unit 4

**URL:** <https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099>\
**Category:** Questions\
**Tags:** data-store, webhooks\
**Created:** [January 17, 2026, 7:53pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099 "2026-01-17T19:53:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Stohler](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mike_stohler/32/86759_2.png) [@Mike\_Stohler](https://community.make.com/u/Mike_Stohler)\
**Post date:** [January 17, 2026, 7:53pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099/1 "2026-01-17T19:53:22Z")

</div>

### 🎯 What is your goal?

Goal is to have MA c01 u04 work to update quantity from 5 to 55

### 🤔 What is the problem & what have you tried?

I have completely redone the second scenario twice, and I can’t figure out what I’m doing wrong. In the Make Advanced C01 C04 it stops at the Data Store and does not make it to the iterator when I click on the link in my email to trigger the module. All of the other modules work, but this last part. The result after I click is “accepted.” Does it have something to do with the “click here” code?

---

<div class="post-metadata">

**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\
**Post date:** [January 19, 2026, 1:20pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099/3 "2026-01-19T13:20:31Z")

</div>

Welcome to the Make community!

We’d love to help, however, we require more information that demonstrates the problem to help us reproduce the scenario and any issues and errors.

To allow others to assist you, please provide the following:

## 1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

- the **full scenario** , and the zoomed in parts of the scenario that you are referring to (if your scenario is huge),
- a **full scenario run/execution** from the history (showing output “speech” bubbles),
- relevant **module fields** (_showing how you’ve used any built-in functions, and how you’ve mapped the variables_),
- relevant filters between modules (_showing which operators and any built-in functions you’ve used, and how you’ve mapped the variables_),
- relevant module input/output bubbles,
- if applicable, any error messages,
- and if applicable, any external services (_spreadsheet headers/ sample data/ regex101.com/ etc. to show the item/ record exists, and is set up correctly_).

> **Need help❓View instructions ◀**
>
> > We would appreciate it if you could directly upload screenshots here instead of linking to them outside of this forum. This allows us to zoom in on the image when clicked, and also having improved privacy from third-party sources.
> > 
> > ## Taking Screenshots
> > 
> > - **Microsoft Windows:** Take screenshots using the “[Windows Snipping Tool](https://support.microsoft.com/en-au/windows/use-snipping-tool-to-capture-screenshots-00246869-1843-655f-f220-97299b865f6b)”, by pressing either PrtSc _or_ WinShiftS keys on your keyboard.
> > - **MacOS:** Take screenshots by pressing CommandShift4 keys on your keyboard.
> > 
> > ## Uploading Attachments
> > 
> > - **Drag** image files directly into the rich-text editor, or
> > - **Click** on the upload button in the editor toolbar to select files:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)

## 2. Scenario Blueprint

Providing your scenario will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return. This would benefit you in implementing our suggestions as you can view screenshots of the changes or paste corrected modules back into your scenario.

> **Need help❓View instructions ◀**
>
> > ## A. Export Blueprint
> > 
> > In the scenario editor, click the three dots at the top-right, then select “ **Export blueprint** ”.  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/1/5/152b265128a71a7a2937c4f701c4beba3f5f610c.png)
> > 
> > - You can upload files and images to this forum by clicking on the upload button:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)
> > 
> > ## B. Create Public Share Link
> > 
> > In the scenario editor, click on the **Share button** :  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/0/a/0ad95b052c1a1651a310868e4eacd432c289022c.png)  
> > Read more about the [scenario sharing feature](https://help.make.com/scenario-sharing) in the Help Centre.

## 3. _Properly-formatted_ Output Bundles from a Scenario Run

Please provide the **input/output bundles** of each of the relevant modules by running the scenario, or get the bundles from a previous run from the Scenario [“History” tab](https://www.make.com/en/help/scenarios/scenario-execution-history).

Providing the bundles from a scenario run will allow others to replicate what is going on, especially if there are complex data structures (nested arrays and collections) and external services. This helps mapping the correct raw variable names from collections (instead of the label/display name).

> **Need help❓View instructions ◀**
>
> > Click on the white speech bubbles on the top-right of each module and select “**Download output (_or input_) bundles**”.  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/2/8/2876156ab3ea5bc9e40bbc0edfb9f025406b7c48.png)
> > 
> > ## A. Upload a Text File
> > 
> > Save each bundle contents in a **plain text** editor as a `moduleNumber-output.txt` file. Open the file to check if it has not added additional formatting or encoded the plain text.
> > 
> > - You can upload files and images to this forum by clicking on the upload button:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)
> > 
> > ## B. Insert a Formatted Code Block
> > 
> > If you are unable to upload files on this forum, alternatively you can **paste the bundles** AND **format them correctly**.
> 
> > # ⚠Formatting IS Important! ⚠
> > 
> > Here are some ways to provide text content in a way that it won’t be modified by the forum.
> > 
> > - **Method 1: Type code fence manually** —  
> > Manually type three backticks ````` in a separate line before and after the content, like this,
> > 
> > - **Method 2: Highlight the pasted content, then click the preformatted text/code button** —  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/7/b/7b91db14846cb99e1084b77e4362a273f8324e74.png)
> > 
> > - **Method 3: Upload your file elsewhere and share the public link** —  
> > This method is only advised for large files exceeding the forum upload limit.

Sharing these details will make it easier for others to assist you, so that you can get better answers, faster.

— @samliew  
P.S.: investing some effort into the tutorials in the [Make Academy](https://academy.make.com) will save you lots of time and frustration using Make!

---

<div class="post-metadata">

**Author:** ![Mike\_Stohler](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mike_stohler/32/86759_2.png) [@Mike\_Stohler](https://community.make.com/u/Mike_Stohler)\
**Post date:** [January 21, 2026, 6:44pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099/4 "2026-01-21T18:44:00Z")

</div>

Hello, here are the scenarios and screenshots.

First and second scenarios seem to work fine. The third one never makes it to the iterator.

this is the inject new data scenaria and it seems to work fine.

 ![Screenshot 2026-01-21 105349](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/4/5/45aa130adb1d7050a094e09587381acae5a88bd5.png)

 ![Screenshot 2026-01-21 105405](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/f/5/f5bfb9ecebb81d7dce835bac9f64984854bf5e94.png)

 ![Screenshot 2026-01-21 105421](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/9/5/952b6af44760a61c15e3e09c66c67b4df51ad0d5.png)

The second scenario seems to work fine. It sends the email

 ![Screenshot 2026-01-21 105031](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/3/8/38443bdfa4e588c84cd54080ea7c5da0f2640660.png)

 ![Screenshot 2026-01-21 105105](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/3/e/3e474458037d4aab4c2e2de7259afcfba36e82e2.jpeg)

The third one gets stuck

 ![Screenshot 2026-01-21 104844](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/6/e/6e7ecf97116d71a507b5fce9c4a098ed046eefa4.jpeg)

---

<div class="post-metadata">

**Author:** ![Mike\_Stohler](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mike_stohler/32/86759_2.png) [@Mike\_Stohler](https://community.make.com/u/Mike_Stohler)\
**Post date:** [January 21, 2026, 6:45pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099/5 "2026-01-21T18:45:05Z")

</div>

![Screenshot 2026-01-21 104931](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/7/5/75c55507d05ec19be89622bc9489b238d7aa0771.png)

 ![Screenshot 2026-01-21 104954](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/e/8/e80bbf34be9f9f278b5eb6db8b07e5d93d10a1e5.png)

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [April 21, 2026, 5:48pm UTC](https://community.make.com/t/make-advanced-data-stores-and-structure-unit-4/101099/6 "2026-04-21T17:48:10Z")

</div>

This topic was automatically closed because it's resolved or inactive. Please, start a new topic.


