Skip to content
Go to Wiise
  • There are no suggestions because the search field is empty.

Wiise Appsource Technical Changes Explained 

Overview: 

This article explains the technical breaking changes introduced in the Wiise Appsource Compliance Update. These changes are primarily required to comply with Microsoft AppSource validation rules and to improve internal code organisation.

Partners and developers with custom extensions may need to update their code before upgrading. 

Types of Technical Changes 

Each change category includes an explanation of what changed and what action may be required. 

Change Type 

What it Means 

Renamed 

The object, field, action, or permission set still exists and behaves the same. Only the internal name has changed to meet Microsoft AppSource naming standards. 

Restructured 

The object has been moved to a different namespace or reorganised internally. Functionality remains the same, but the reference path used in code has changed. 

Removed 

A procedure or object has been removed with no direct replacement. Any custom extension calling this must be updated before upgrading. 

Object and Field Names Renamed  

Change Type 

Renamed 

Validation Rules 

AS0030, AS0032, AS0005 

Affected 

• 877 field and control names renamed 
• 5 object names updated 
• Changes affect both the Wiise Base App and Australia and New Zealand Extensions 

Many internal Wiise objects and fields now include the KBIZ prefix to meet Microsoft AppSource naming requirements. 

Action required 

Partners and developers must: 

  1. Update AL code referencing renamed objects or fields 

  2. Replace old identifiers with the new KBIZ prefixed names 
  3. Recompile extensions 
  4. Test in a sandbox environment before upgrading production 

Actions and ActionRef Renamed 

Change Type 

Renamed 

Validation Rules 

AS0031 

Affected 

133 action references across Base App and AU/NZ Extension. These include Approval Workflows, EFT processes, Expense integrations, Timesheets, Landed Cost, Sales and Order processing. 

All renamed actions now include the KBIZ prefix. 

Action required 

Partners must update ActionRef references in custom extensions. 

Special attention should be given to approval Workflow actions such as:

  • Send,

  • Cancel,

  • Approve,

  • Reject

  • Delegate.  

AU and NZ integration actions such as:

  • ImportBankFeeds, 

  • EFTDocument, 

  • ExpenseExternalLink

  • EditTimeSheets 

should also be reviewed. 

Namespace Reorganisation 

Change Type 

Restructured 

Validation Rule 

AS0007 

Affected 

33 objects in Base App,  primarily PowerBI pages and queries moving to Wiise.PowerBI; Automation codeunits to Wiise.Automation; Warehouse objects to Wiise.Warehouse 

Why? 

Some Wiise objects were previously located in generic namespaces, which made it harder to manage and maintain module boundaries as the product expanded. 

To improve organisation and align with AppSource best practices, these objects have been moved into clearer, purpose specific namespaces such as: 

Wiise.PowerBI, Wiise.Automation, Wiise.Warehouse, and Wiise.Purchases. 

This change affects only the internal reference paths used in code. Functionality remains unchanged. 

Action required 

Partners must update namespace references in dependent extensions. Replace older namespace paths with the new namespaces when declaring or referencing objects in AL code. 

Permission Sets Renamed  

Change Type

Renamed 

Validation Rule 

AS0090 

Affected 

9 AU permission sets and 1 report. All WIISE AU/NZ permission sets renamed to KBIZ AU/NZ 

Why? 

AppSource validation rule AS0090 requires permission sets to carry the publisher prefix for uniqueness across the AppSource ecosystem. The WIISE AU/NZ prefix is being replaced by KBIZ AU/NZ to align with the publisher identifier registered with Microsoft. Permissions granted by these sets are unchanged. Only the permission set names have changed.  

Action required 

System administrators must reassign users from the old WIISE AU/NZ permission sets to the corresponding KBIZ AU/NZ permission sets after the upgrade. Partners should also update any custom extensions that reference the old permission set names. 

EFT Management Procedure Removed  

State 

Removed 

Validation Rule 

AS0018 

Affected 

Codeunit 16034604 KBIZ EFT Management procedure: UpdateVendLedgerEntryExportToPaymentFile(Record "Gen. Journal Line", Boolean) 

Why? 

The EFT processing logic has been updated within the KBIZ EFT Management codeunit, and the system no longer requires this procedure as a public method. 

EFT payment file export functionality continues to operate as expected. 

This change only affects extensions that call this specific procedure. 

Action required 

Partners must: 

• Identify any extensions calling this procedure 
• Remove or replace the call before upgrading 

Deployment Checklist 

The following checklist is recommended to ensure a smooth upgrade to the latest Wiise version. 

Before Deployment 

Before upgrading production, complete the following steps: 

  1. Back up the production environment 
  2. Ensure all dependent extensions are updated to reference new object and field names 
  3. Deploy the update to a sandbox environment first 
  4. Install updated dependent extensions in sandbox 
  5. Test core business workflows: Sales, Purchase, Inventory, Finance 
  6. Validate integrations: Banking, Payroll, Timesheets, E-Commerce 
  7. Test all external APIs connecting to Wiise 
  8. Review and reassign security roles to new KBIZ AU/NZ permission sets 
  9. Confirm UDF (User-Defined Field) data is intact after sandbox upgrade. 

Tip: Always complete sandbox testing before upgrading production to ensure customisations and integrations continue to function as expected. 

During Deployment 

When upgrading production: 

  1. Schedule upgrade during a low usage period 
  2. Notify all users of expected downtime window 
  3. Ensure a rollback plan is available in case of unexpected issues 
  4. Monitor telemetry and error logs during the upgrade process 

Note: End users will not notice any functional or interface changes after the upgrade. 

After Deployment 

After the upgrade is completed: 

  1. Validate data integrity across all key tables 
  2. Test critical business processes end-to-end 
  3. Confirm all external integrations are functioning correctly 
  4. Verify that users have the correct access using the new KBIZ AU/NZ permission sets 

 Key Functional Areas Affected 

The following functional areas contain the largest concentration of internal naming changes. 

These updates affect internal identifiers only and do not change system behaviour. 

  1. User Defined Fields (UDF) 
  2. PowerBI Integration 
  3. Approval Workflows 
  4. Extension Integrations 
  5. Role Centre Customisations 

1. User-Defined Fields (UDF) 

Approximately 640 internal field references are being renamed across Sales, Purchase, Job, and Inventory pages. This is the largest category of change and affects custom field controls on all major transactional pages.  

Note: No data is lost during the upgrade. Mapping is handled automatically by Wiise upgrade codeunits. 

2. Power BI Integration 

All Power BI related pages and queries have been moved to the Wiise.PowerBI namespace. This improves organisation and aligns with Microsoft AppSource best practices. 

However, extensions referencing these objects using their previous namespace paths will need to be updated. 

3. Approval Workflows 

A total of 91 action references in the Base App are renamed. These actions are primarily used in approval workflows such as Item Journal, Warehouse Journal, Purchase Order, and Purchase Invoice approval workflow actions.  

Note: Approval workflow behaviour remains unchanged for end users. 

4. Australia Extension Integrations 

Several Australia specific integrations include renamed objects and actions. 

Examples include: 

  • EFT and Bank Feeds (8 actions renamed) 
  • Expense integrations (16 actions renamed) 
  • Timesheets (8 actions renamed) 
  • E-commerce / Shopify integrations (10 field references renamed) 

Additionally, the EFT Management codeunit has had one procedure removed, which must be updated in any extension calling it.  

5. Role Centre Customisations 

Several Role Centre panels have been refactored including: 

CommandCentrePanel, DashboardsPanel, TimesheetPanel, BankFeedsPanel, and PayRunPanel.  

Extensions that add content or functionality to these panels may require updates. 

 

  1. You now understand the technical changes introduced in this release, the actions required by partners and developers, the deployment checklist for a safe upgrade, and the key functional areas affected.

What’s next? 

Find out how to Install Wiise App Updates. 

 

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.