Budget Account Descriptions

I am attempting to create a workflow where a form is began to define expense categories, the responses are recorded by a manager, then the responses automatically update the budget dataset in an ETL process.

In between the recorded responses and the automatic update of the ETL is about 7 days, as that is the length of time we designate to run our GL data. I want to be able to, in an app, have managers record a form and instantly see their pending descriptions, so that they do not update and wonder where their work went. Then, when the GL data / ETL updates, I want to remove those responses from the recorded response.

I have created the form, but have no idea how to query the responses correctly. I do not understand why the append to dataset function has the selections that it does. Any guidance, preferably with some kind of visual aid, would be very welcome.

Best Answer

  • DanHendriksen
    DanHendriksen Domo Employee
    edited April 11 Answer ✓

    1 - That works.

    2 - No, they do not. It will write them to whatever dataset you instruct it to.

    3 - You could have a function make a UUID and then include it in what you pass to the dataset. You can also grab metadata from the workflow, such as who started the workflow and include it in what you write to the dataset.

Answers

  • DanHendriksen
    DanHendriksen Domo Employee

    Append to dataset looks for a delimiter, a dataset and values. The dataset is what you want to append to. The values is a list of values to write to a dataset. If your dataset has 5 columns, you need to write 5 values. The delimter is to allow you to stipulate what seperates your values. Comma is default, but sometimes your values have commas.

    So if you want to write 3 values to a dataset, you could have your values be:

    value 1, value 2, value 3

    And your delimiter would be a comma. However, if one of your values had a comma in it, using comma as a delimiter would return more than 3 columns.

    value,1, value 2, value 3

    for example would show up as 4 columns. In that case, you'd want to use a different delimiter, like maybe a pipe. So you could pass

    value,1|value 2|value 3

    with a | as the delimiter and it would write 3 values to your 3 columns.

    Does that make sense?

  • DanHendriksen
    DanHendriksen Domo Employee

    Typically folks will you use the string builder to create their list of values. You can select CUSTOM and then insert variables.

    {{variable1}} | {{variable2}} | {{variable3}}

    Then pass a pipe as the delimiter. Hopefully that makes sense.

  • DanHendriksen
    DanHendriksen Domo Employee

    Last thing I will say, is that AppDB is often easier for things that you might want to update. So if you're capturing these and logging them to exist forever more, an append to a dataset is great. If you want to update those values later, LMK and we can talk about AppDB.

    1. Assuming a -- delimiter, is this the correct way to write this to update columns 1, 2, and 3 in the dataset?

    2. Do the form responses generated in a workflow have a designated dataset, like the ones in Apps? The pictured dataset was the API response dataset from a different form.

    3. I do not want to update the record once it has been made. I just want to record the row with a unique row ID, along with when and who recorded it, and their responses.

  • DanHendriksen
    DanHendriksen Domo Employee
    edited April 11 Answer ✓

    1 - That works.

    2 - No, they do not. It will write them to whatever dataset you instruct it to.

    3 - You could have a function make a UUID and then include it in what you pass to the dataset. You can also grab metadata from the workflow, such as who started the workflow and include it in what you write to the dataset.