Bot creating two records instead of one as it should

[Nicolas_Feldman]

Hi everyone, im trying to build a Bot that every last day of the month creates a New Row on a Table with certain data.

The problem im having is that when the Bot runs, it creates TWO rows:

- the first with only the UniqueID column filled (which is the only column with formula on the table),

- and then a second row with the values I have set on the Process.

The way I set up the bot  is a Scheduled trigger for every last day of the month + a process that adds a new row with X values.

Anyone know why this behavior and how to avoid it?

[WillowMobileSys]

It looks like your process has 2 steps.  The first step is "Call a process".  This step is intended to branch out to another pre-define Proces - set of steps.  Is this something you are doing intentionally?  If so then waht are the steps in that other Process?

Otherwise, if your intention is to simply add a row, then you only need the second step "Run a data action" as the only step in  THIS process.

I hope this helps!

[Nicolas_Feldman]

Thank you @WillowMobileSys , I see what you mean. Although I cant seem to choose "run a data action" from the bot, instead I am calling a process that allows me to add a new row.

See screenshots for the Bot and for the Process.

[WillowMobileSys]

This usually occurs because the Process was added without a Table specified.  You need to go to the SAVED process and update it to the Table that matches the Event.

To get to the list of Processes, hver over the Bots icon in the left-hand side Menu.  Then tap on Processes.

Find the Process int he list and open it.  At the top is the Table field.  Update or adjust it to the Table name used in the Bot Event section.

I hope this helps!!

[Nicolas_Feldman]

Thanks @WillowMobileSys  for helping me figure this out.

The thing is since the "event" in the bot a scheduled type happening every last day of the month, there is no table to be selected for the bot.

What do you recommend in this case?🤔

[WillowMobileSys]

Your data action is adding a row to a specific table.  THAT is your table and your Event should be designated with this same table as well.  It will not change HOW the Scheduled Event is triggered.

[Nicolas_Feldman · Accepted solution]

Thanks @WillowMobileSys I figured it out,  I had to delete the first step of the process, and leavy only the add option in the bot. This way its not duplicating records.

[WillowMobileSys]

LOl!  I did mention this in my first post!  I couldn't recommend specifically to delete the first step since I didn't know what your intentions were.  But glad you finally got there!!

[sjbrown]

I'm a little confused about what exactly needs to be deleted. I have the same set up; Bot created with the event source as "Scheduled", and then "Daily" is the schedule. The next step is "call a process", and the process has the correct table designated with one step "add a row". 
I don't understand what the solution means when they said "Leave only the add option in the bot". None of the other options under "run this process" appear to just be adding a row?