Administering Cloud EPM: The Platform Beneath the Business Processes · Module 11 · Automation
Scripting patterns: data load and refresh
Lesson 127 of 201 · 13 min
Build a load script: sign in, upload the file, run the import job, refresh, sign out. Add a check that the file exists before uploading. Add a check on job status before proceeding to the next step. Run it and show it succeeding, then break it deliberately — a bad file — and show it failing at the RIGHT step. CHECK BEFORE YOU ACT, AND CHECK AFTER. A script that uploads a missing file and refreshes anyway has done something WORSE than nothing. SEQUENCE MATTERS. Load, then import, then refresh. Getting it wrong produces a refresh of yesterday's data with today's timestamp — the kind of error nobody catches for a month. The deliberate failure is the lesson. It shows what a well-built script does when the world is wrong.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 11 · Automation
- 1Three tools, one questionFree preview
- 2Job Scheduler
- 3Installing and configuring the automation utility
- 4Authentication and credential handling
- 5The command surface
- 6Scripting patterns: backup and export
- 7Scripting patterns: data load and refresh
- 8Error handling and logging
- 9Scheduling and service accounts
- 10REST APIs and when to reach for them
- 11The integration agent
- 12What breaks
- 13Lab: automate it, and write the runbook
