Wiise AppSource Compliance Update
Overview:
- Learn about Wiise AppSource Compliance Update
Note:
-
This is a technical compliance update only.
-
There are no functional, user interface, or data changes.
- This feature is available in Business Central Version 27.3 and from Wiise app version 27.3.3.0
- Your IT Administrator will need to install the latest Wiise app updates.
Why is this update required?
Wiise is releasing an update to comply with Microsoft AppSource validation requirements in the March 2026 release.
This update introduces internal technical changes across the Wiise Base App, Wiise Australia App and Wiise New Zealand App to meet Microsoft naming and publishing standards.
These changes include updates to internal object names, namespaces, and permission sets used by Wiise extensions.
Note: Customers and partners who have built customisations, extensions, or integrations on top of Wiise will be directly impacted by this release and must test their solutions in sandbox before upgrading their production environment.
|
✅ What is NOT changing
|
⚠️ What IS changing (Technical Changes)
Note: These changes primarily affect partners and customers who have built customisations or integrations on top of Wiise |
Why the Wiise AppSource Compliance Update?
Microsoft requires all applications published on Microsoft AppSource to follow strict naming conventions and structural standards.
These rules ensure:
-
Unique naming across the Microsoft ecosystem
-
No conflicts between extensions from different vendors
-
Long term platform stability and maintainability
This update brings Wiise into alignment with these AppSource requirements.
Scope of Changes
During validation, Microsoft identified over 1,169 AppSource compliance issues that required updates. To resolve these, Wiise has updated internal identifiers across the Wiise Base App, Wiise Australia App, and Wiise New Zealand App.
Note: These updates affect only the internal code structure, not how the system works for users.
|
Change Category |
Base App |
AU App |
NZ App |
Total |
|
Object/Field Renames (AS0032) |
762 |
115 |
82 |
959 |
|
Actions & ActionRefs Renamed (AS0031) |
91 |
42 |
16 |
149 |
|
Namespace Changes (AS0007) |
33 |
0 |
0 |
33 |
|
Permission Sets / Reports Renamed (AS0090) |
0 |
10 |
9 |
19 |
|
Objects Renamed (AS0030) |
1 |
3 |
3 |
7 |
|
Table Field Renamed (AS0005) |
1 |
0 |
0 |
1 |
|
Procedure Removed (AS0018) |
0 |
1 |
0 |
1 |
|
TOTAL |
889 |
161 |
112 |
1,169+ |
Who needs to take action?
This update may impact different groups in different ways. Use the guidance below to determine whether action is required for your business.
Select the option that best matches your role:
End Users
Note: No action is required
End users will not experience any change in:
- Screens
- Workflows
- Reports
- Business processes
Tip: After the upgrade, Wiise will look and behave the same for end users.
Customers Using Standard Wiise Only
Note: Minimal action is required
If you are using standard Wiise without any custom extensions or integrations, the impact is minimal.
You’ll need to:
- Deploy the update to a sandbox environment
- Run through key business workflows
- Confirm user access and permissions
Note: Administrators will also need to reassign users to the new permission sets introduced in this update.
Partners and Customers with Customisations
Note: Action required
Customers with custom solutions or external integrations should validate their environment before upgrading to production.
Please refer to the following sections for guidance when assisting customers who have customisations:
Tip: Even though functionality is unchanged, sandbox testing ensures your environment continues to operate as expected.
Examples of Customisations That May Be Impacted
This may include:
- AL extensions built on the Wiise Base App
- Partner add ons or vertical solutions
- Power Automate flows referencing Wiise fields
- Logic Apps integrations
- External API integrations
- Third party integrations such as:
- EFT
- Timesheets
- E-commerce platforms
What Partners and Developers Need to Do
Partners and developers must update their customer's custom solutions to reference the new identifiers introduced in this release.
Please review the following sections in this article for detailed guidance:
Required Actions
Partners and developers should complete the following steps before upgrading production::
- Identify all customisations, extensions and integrations referencing Wiise objects or fields
- Update references to the new KBIZ prefixed identifiers
- Update namespace references
- Update permission set references
- Wiise AU to KBIZ AU naming
- Wiise NZ to KBIZ NZ naming
- Review the removed EFT procedure if used in custom extensions
- Recompile extensions
- Deploy updated extensions to sandbox environment on the latest Wiise version.
- Perform full end to end testing.
- Upgrade production once all customisations have been validated in sandbox.
Note: You may want to test all customised workflows, approval processes and integration touchpoints
Note for Partners: Please communicate your extension readiness timeline to your customer before they schedule their production upgrade
High Risk Areas to Test
You’ll need to prioritise testing in the following areas:
- Approval workflows
- Wiise Custom Fields (UDF)
- Power BI integrations
- EFT integrations
- Role Centre panels
- Permission Set Renaming
1. Approval workflows
A total of 133 workflow action references were renamed. You’ll need to review actions such as: Send, Cancel, Approve, Reject and Delegate.
2. Wiise Custom Fields or User Defined Fields (UDF)
Over 640 field references across: Sales, Purchasing, Inventory and Jobs were renamed internally and continue to function normally.
3. Power BI integrations
All Power BI objects have been moved to the Wiise.PowerBI namespace. Extensions referencing older namespaces must be updated.
4. EFT integrations
The following procedure has been removed: UpdateVendLedgerEntryExportToPaymentFile. Any extensions calling this procedure must be updated. Find out more about this in Wiise Appsource Technical Changes.
5. Role Centre panels
Several panels were refactored including: CommandCentrePanel, DashboardsPanel, TimesheetPanel, BankFeedsPanel and PayRunPanel.
Extensions that modify these panels may require updates.
6. Permission Set Renaming
Permission Set Renaming Reference – Wiise Australia
The following AU permission sets have been renamed. Customers must update user assignments after the upgrade.
|
Old Permission Set Name |
New Permission Set Name |
|
WIISE AU ANALYTICS |
KBIZ AU ANALYTICS |
|
WIISE AU TIMESHEETS |
KBIZ AU TIMESHEETS |
|
WIISE AU SETUP |
KBIZ AU SETUP |
|
WIISE AU FULL ACCESS |
KBIZ AU FULL ACCESS |
|
WIISE AU BANKING |
KBIZ AU BANKING |
|
WIISE AU BASIC |
KBIZ AU BASIC |
|
WIISE AU BASIC SALES |
KBIZ AU BASIC SALES |
|
WIISE AU SALES CHNL |
KBIZ AU SALES CHNL |
|
WIISE AU PAYROLL |
KBIZ AU PAYROLL |
Permission Set Renaming Reference – Wiise New Zealand
The following NZ permission sets have been renamed. Customers must update user assignments after the upgrade.
|
Old Permission Set Name |
New Permission Set Name |
|
WIISE NZ ANALYTICS |
KBIZ NZ ANALYTICS |
|
WIISE NZ TIMESHEETS |
KBIZ NZ TIMESHEETS |
|
WIISE NZ SETUP |
KBIZ NZ SETUP |
|
WIISE NZ FULL ACCESS |
KBIZ NZ FULL ACCESS |
|
WIISE NZ BANKING |
KBIZ NZ BANKING |
|
WIISE NZ BASIC |
KBIZ NZ BASIC |
|
WIISE NZ BASIC SALES |
KBIZ NZ BASIC SALES |
|
WIISE NZ SALES CHNL |
KBIZ NZ SALES CHNL |
|
WIISE NZ PAYROLL |
KBIZ NZ PAYROLL |
Note: Permissions themselves are unchanged. Only the permission set names have been updated.
Note: To ensure a smooth transition to the new Wiise version, partners and customers should familiarise themselves with the breaking changes explained and the deployment checklist. You can then complete testing in a sandbox environment before upgrading production.
What’s next?
Find out more about Wiise Appsource Technical Changes.
Need more help?
No problem, that's what we're here for. Reach out to support@wiise.com anytime you can't find what you're looking for.