Workforce Engagement Management

 View Only

Sign Up

  • 1.  Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 20 days ago

    Has anyone else seen a change this week to the Time-Off Requests export?

    Two things changed on our side:

    • Datetime fields now include a comma (e.g. 07/31/2026, 12:00 AM)
    • Column name changed from "Activity Code Name" → "Activity Code"

    Because it's a CSV and the datetime fields aren't quoted, the comma is being treated as a delimiter and breaking parsing (columns shift, imports fail).

    This isn't mentioned in the June 1 release notes, so trying to confirm:

    • Is this intentional?
    • Or is this a bug/regression in the export output?

    This breaks downstream imports pretty quickly, so want to know if we should fix around it or expect a rollback.


    #Reporting/Analytics
    #WEM-Quality,WFM,Gamification,etc

    ------------------------------
    James Rowberry
    Manager
    ------------------------------


  • 2.  RE: Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 17 days ago

    Hello James,

    I am going to move this to the WEM Community as the experts there will be better placed to answer this



    ------------------------------
    Sam Jillard
    Online Community Manager/Moderator
    Genesys - Employees
    ------------------------------



  • 3.  RE: Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 17 days ago

    Hi James, 
    Could you please raise a care ticket for this?
    I've investigated with the team to see if this was an intended change or a side effect of the newer date/time formatting rules. 

    thanks, 

    Paul



    ------------------------------
    Paul Wood
    Genesys - Employees
    WFM Product Manager
    ------------------------------



  • 4.  RE: Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 14 days ago

    Hi Community, 

    The change to the "presentation date/time" columns 4 and 6 is reflective of the wider localisation date formats that we are rolling out across the platform.
    We'd recommend using the  ISO formated dates in columns 3 and 5 for any external processing/reporting. 

    While the new localisation of the date/time can result in a "," being added within the date and time format, it will not interfere with the CSV formating is the value is fully delimited with double quotes.

    Paul



    ------------------------------
    Paul Wood
    Genesys - Employees
    WFM Product Manager
    ------------------------------

    Original Message


  • 5.  RE: Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 14 days ago

    Hi Paul,

    Thanks for the clarification, that's helpful context on the localization changes.

    I think the main gap we ran into here is around change visibility rather than the change itself. This update had a direct impact on downstream processing (CSV parsing + schema changes), but it wasn't called out in the release notes, so there was no opportunity to assess or prepare for that impact in advance.

    For teams using exports as part of operational workflows or integrations (even if not API-based), changes like:

    • introducing delimiters within fields
    • modifying column names

    can have immediate downstream effects.

    Is there (or could there be) a way for release communications to better highlight export/schema-impacting changes specifically? Even a simple flag in the notes would go a long way in helping teams like ours stay ahead of these.

    Appreciate the guidance on using ISO columns.

    Thanks,
    James



    ------------------------------
    James Rowberry
    Manager
    ------------------------------

    Original Message


  • 6.  RE: Did anyone else see CSV export formatting change for Time-Off Requests?

    Posted 14 days ago

    Thanks for the feedback @James Rowberry.
    Yes, this is certainly something we can add to the release notes and announcements. In this instance, I have to hold my hands up for missing adding the change to the communications. 




    ------------------------------
    Paul Wood
    Genesys - Employees
    WFM Product Manager
    ------------------------------

    Original Message


Related Content