Skip to main content
Question

Date field not populating with Automations - trying to copy a week's worth of time sheet data for the next week

  • June 18, 2018
  • 0 replies
  • 127 views
I'm attempting to allow the users to copy their time sheet records from one week to the next as a means to pre-populate their time sheets. At this time, I have my automation create a new record and copy the Related Project and the Related Employee successfully. However, there is a Formula Date Field called "+7 days" that takes the time sheet Date field and adds 7 days to it. When I try to have this "+7 Days" date copied over to the new record Date field, it comes in blank. Not sure how to get the automation to populate the Date field with this future date as intended.
    This topic has been closed for replies.

    • EOMDevelepors
    • Quickbase Alumni
    • June 18, 2018
    Automatons were limited to date fields. 
    • LeeSGilmore
    • Author
    • Quickbase Alumni
    • June 19, 2018
    At this time, I'm using a check box to trigger the automation. When the record is saved with a specific checkbox checked, it then creates a new record with the same Project and Employee. Ideally it would also have a date field populated with the old record's date +7 days. This is where I'm stuck, the date field is blank after the action is run.
    • EOMDevelepors
    • Quickbase Alumni
    • June 19, 2018
    Create a date formula:

    [your date field]+Days(7)

    In your automation set the value of the date field in your new record with the data of the new formula value of your old record.
    • LeeSGilmore
    • Author
    • Quickbase Alumni
    • June 19, 2018
    I believe I've done this but the date field is not populating after the automation is triggered. I'm going to submit a trouble ticket with QB to see if they can identify the issue. I appreciate your time in troubleshooting this with me.
    • LeeSGilmore
    • Author
    • Quickbase Alumni
    • June 20, 2018
    After working with the Support Team, we were able to get it to work properly. The method wasn't changed so it seems there was a glitch in the first Automation I created. After building a whole new automation we were able to get it to work.
    Terms & ConditionsAccessibility statement