Change subscriptions
Background runs
Run holds, terminations and batch changes of whole fleets in the job queue, follow them on Background Runs and My Notifications, and run reports on large books.
updated: applies-to: 1.3.5.0
A hold or a termination of a contract with thousands of lines, or a batch change of a whole customer base, can take minutes. Instead of making you wait, Bitta Subscriptions offers to run it in the background, in Business Central's job queue, and tells you when it is done. Reports that read the whole book ask for a filter first when the book is large.
Use it for large customers: a contract with 5,000 devices or seats, or a price change for every subscription of a plan.
Before you start
On the Bitta Subscriptions Setup page, group Large Volumes:
- Background Line Threshold (500 by default): from how many subscription lines a hold or termination, or from how many ready lines a batch change, is offered as a background run. Leave it blank to always run while you wait.
- Email Background Results: also email the result to the user who started the run, to the email address in that user's User Setup only. A note in My Notifications is always added.
- Large Book Contracts (1,000 by default): from how many customer contracts the whole-book reports ask for a filter first. Leave it blank to never ask.
The job queue must be running. The run uses the permissions and the work date of the user who started it.
To run a change in the background
- Finish the hold or termination wizard, or choose Apply on a batch change, as usual.
- When the change covers more lines than the threshold, Business Central asks how to run it. Choose In the background (recommended). Now and wait here runs it at once as before.
- The message gives the run's number. You can keep working.
When the run is done you get a note in My Notifications (on the role center), and an email if the setup says so.
To follow background runs
Search for Background Runs, choose the Failed Background Runs cue, or open Background Runs from the menu of the Subscription Lifecycle Manager role center. Each run shows its Type (Hold, Termination or Batch Change), Status (Queued, Running, Completed or Failed), No. of Lines, Lines Processed, Result No. and Error.
- Open Result opens the hold, termination or batch change that the run created or applied.
- Job Queue Entry opens the job queue entry while the run waits or runs.
A hold or termination is written in one transaction: Lines Processed shows all lines when it completes, and nothing is written when it fails. Fix the problem in Error, then start the change again from the wizard. A batch change counts its lines as they are applied.
The Failed Background Runs cue on the role center counts failed runs.
Reports on a large book
The Schedule of Services, Contract Value and Backlog, Billed Ahead and Unbilled, Subscription Margin, Billing and Revenue Forecast and Churn and Retention reports read every contract. When the company has more contracts than Large Book Contracts:
- the request page shows a hint with the number of contracts;
- without a filter, the report stops and says to filter on a contract, customer or reseller, or to turn on Whole Book and choose Schedule, so the report runs in the job queue and you get it when it is ready.
Churn and Retention starts with the last 3 months. The figures do not change; only the defaults do.
What happens in Microsoft Subscription Billing
- The background run calls the same engines as the wizard, with the same checks. Microsoft's subscription lines change exactly as they would in the foreground.
- A change that needs approval is not queued: it gets an approval request (Approvals and the contract lock).
Limits
- A failed hold or termination cannot be started again from the Background Runs page. Start it again from the wizard.
- The email goes only to the address in the user's own User Setup.
See also
- Hold and resume, Terminate and reopen
- Charges and batches: batch changes
- Device register