Tooling & Testing

Originally posted by Mohsen Askari on September 16, 2025 at 3:31 PM. Did you know that we can now use the Quick Entry Functionality within payroll for one time payments, instead of adding payroll elections within People?

Originally posted by Sukal Mondal on October 20, 2025 at 3:38 PM. PATCH Call Error When Deleting SchedulesOne of our partners recently ran into an issue while trying to delete a schedule via a PATCH call. The API returned:“You are no longer able to make one or more of the submitted changes.”The timesheet wasn’t locked, the pay period was open, and all the right permissions were in place — but the error persisted. 💡 Expert TipSometimes permissions look fine, but a subtle difference in date context or role access can block a delete. It’s always worth testing if the same user can perform the delete in the Dayforce UI — this helps isolate whether it’s a data permission or API-layer restriction. Open Questions for the CommunityHave you seen this message before when deleting schedules or shifts?Was it tied to effective dates or approval states?Any patterns or workarounds you’ve found that resolve it?👉 Drop your insights — let’s build a quick troubleshooting checklist for this one.

Originally posted by Sukal Mondal on October 20, 2025 at 3:43 PM. Batch Processing KPI Data – Is It Possible?A client is looking to post KPI data for hundreds of locations — roughly 12,000 calls per day (500 sites × 24 hours). They’re exploring whether the KPI endpoint can handle batch submissions or if it requires one call per record. 💡 Expert TipWhile the KPI Data endpoint isn’t explicitly documented for batching, you can test structured JSON arrays and leverage HTTP batching libraries (for example, in Python or C#) to optimize calls.Endpoint: /{clientNamespace}/V1/KpiDataRequest Body: JSON array of KPI records Open Questions for the CommunityHas anyone successfully implemented batching or bulk posting for KPIs?What approaches worked best for high-frequency data — queue-based, scheduled jobs, or custom aggregation before posting?Any performance metrics you can share?Let’s compare methods for scaling large KPI workloads efficiently.

Originally posted by Jeff Dooley on May 26, 2026 at 2:32 PM. Hello, I am currently testing the Dayforce AI Assistant in a sandbox environment. For testing purposes, I disabled the option to use Dayforce User Guides so the assistant relies primarily on Hub media documents and Hub text content. The assistant is successfully returning information from older published Hub content and is working well; however, newly published Hub documents and text do not appear to be available to the assistant yet. I have reviewed and followed the recommendations in the “Best Practices and Troubleshooting Guide for Dayforce Assistant” to create content and text for AI consumption. I also came across this article indicating that Hub documents may not appear in assistant search results if indexing has not completed properly:My question is whether there is a process, scheduled job, or support-triggered action available to force or refresh indexing for Hub content so newly published documents become searchable