Writeback
mcCalendar Writeback
Overview
Power BI is a read-only environment when it comes to persisting edits back to your source system. Reports can display data and capture interactions, but they cannot directly write changes into your database or line-of-business application.
How mcCalendar solves this
mcCalendar is tailored with full writeback capability. You configure an API endpoint, and the visual will execute full CRUD operations against that API as users work in the report.
- Create events via an HTTP POST.
- Update events via an HTTP PUT.
- Delete events via an HTTP DELETE.
- Read operations are typically handled by your dataset refresh (the report reads from your model), while write operations persist through your API.
Metadata: the context that makes events actionable
Not every useful detail belongs in the mandatory calendar fields. That’s why mcCalendar supports Metadata: additional columns you drop into the Metadata bucket in Power BI. Think of it as the “everything else” that turns a time block into a real work item.
- Optional, but valuable: task name or ID, assignee (name / ID), notes, description, tags, links, attachments, and more.
- Editable by design: if a field is present in the Metadata bucket, it becomes editable in the event dialog.
- Type-aware inputs: mcCalendar detects each field’s data type and presents the right edit control automatically.
- Included in writeback: when users create or update an event, those Metadata values are sent along to your API as part of the writeback payload.
Writeback service & support
For writeback service description, documentation, implementation details, and support, please contact support@mormitech.com.
Optional API work
Writeback is included with mcCalendar free of charge. If you need a custom-tailored API — creation, hosting, and planning by Mormitech — that is available as a separate agreement. Contact support@mormitech.com to discuss options.