This is a build-to-order extension, not an instant download. After a short scoping call to confirm which lists, fields, validation rules, and permission sets you need, a typical build runs about one working week depending on how many tables and custom rules are involved. ECOSIRE then installs it as a per-tenant extension on your Business Central environment (cloud SaaS or on-prem), configures permissions, and walks your team through it. You receive the .app package and the AL source on handover.

Every build includes a post-delivery support window for bug fixes and questions. Because it ships as a per-tenant extension that doesn't modify base BC objects, it survives Microsoft's monthly and major BC updates cleanly; if a future BC release changes an API or table we depend on, we patch the extension under support. Beyond the initial window, you can add new lists, fields, or rules as scoped change requests, or take an ongoing maintenance agreement.

Yes — that's the core design. Imports land in a staging table first and run the same AL field validation, table relations, and posting-group checks as the standard BC pages, so invalid rows are rejected with a reason instead of corrupting your tables. You review a row-by-row old-value → new-value change preview before anything is committed, and a committed batch can be rolled back, including reversal of posted entries where applicable.

Yes. Because we build the extension against your specific environment, we can target standard tables (Items, Customers, Vendors, prices, dimensions) and any custom or ISV tables and fields you ask us to scope, as long as they're accessible via AL and the BC API. We confirm the full list during scoping so the export sheets and validation match your real data model.

Standard BC can open a list in Excel and even edit-and-publish simple cases, but it doesn't give you reusable mass-update rules (percentage math, conditional find/replace), a saved template library, a pre-commit change preview, batch rollback, Job Queue offloading for large runs, or permission-scoped control over who can do it. This tool packages all of that as one governed, validated workflow built around your environment.