Skip to content

Conversation

@sthompson-queue
Copy link

@sthompson-queue sthompson-queue commented Jan 30, 2026

Summary

Add Avalara integration features including new tables, pages, and extensions

  • Created "AvalaraInput Field" table to store input field configurations for Avalara documents.
  • Added "Avalara Input Fields" page for managing input fields associated with Avalara mandates.
  • Extended "Posted Sales Credit Memo" and "Sales Credit Memo" pages to include "Avalara Doc. ID" field visibility based on mandate presence.
  • Introduced "Avalara Sales Header" and "Avalara Sales Cr.Memo Header" table extensions to store Avalara document IDs.
  • Added "Avalara Trans. Rule Type" enum extension for Avalara-specific transformation rules.
  • Enhanced "Data Exch Field Mapping Part" page with a default value field.
  • Extended "E-Doc. Service Data Exch. Sub" page to support Avalara-specific field mapping.
  • Updated "E-Documents" page with actions for receiving and downloading documents from Avalara.
  • Implemented "Maintenance" codeunit for processing E-Documents and handling download errors.
  • Created "Media Types" and "Message Event" tables for managing media types and message events from Avalara API.
  • Developed "Message Events Subform" and "Message Response Card" pages for displaying message events and responses.
  • Extended "Transformation Rule" table to include advanced lookup configurations for Avalara.
  • Updated "Transformation Rules" page to conditionally display fields based on transformation type.

Work Item(s)

Fixes #6385
Avalara commissioned changes to how the integration works, discussed with Magnus

…ensions

- Created "AvalaraInput Field" table to store input field configurations for Avalara documents.
- Added "Avalara Input Fields" page for managing input fields associated with Avalara mandates.
- Extended "Posted Sales Credit Memo" and "Sales Credit Memo" pages to include "Avalara Doc. ID" field visibility based on mandate presence.
- Introduced "Avalara Sales Header" and "Avalara Sales Cr.Memo Header" table extensions to store Avalara document IDs.
- Added "Avalara Trans. Rule Type" enum extension for Avalara-specific transformation rules.
- Enhanced "Data Exch Field Mapping Part" page with a default value field.
- Extended "E-Doc. Service Data Exch. Sub" page to support Avalara-specific field mapping.
- Updated "E-Documents" page with actions for receiving and downloading documents from Avalara.
- Implemented "Maintenance" codeunit for processing E-Documents and handling download errors.
- Created "Media Types" and "Message Event" tables for managing media types and message events from Avalara API.
- Developed "Message Events Subform" and "Message Response Card" pages for displaying message events and responses.
- Extended "Transformation Rule" table to include advanced lookup configurations for Avalara.
- Updated "Transformation Rules" page to conditionally display fields based on transformation type.
@sthompson-queue sthompson-queue requested review from a team as code owners January 30, 2026 14:43
@github-actions github-actions bot added Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork labels Jan 30, 2026
@github-actions
Copy link

Issue #6385 is not valid. Please make sure you link an issue that exists, is open and is approved.

@sthompson-queue
Copy link
Author

@microsoft-github-policy-service agree [company="Queue Associates"]

@sthompson-queue
Copy link
Author

@microsoft-github-policy-service agree company="Queue Associates"

@Groenbech96
Copy link
Contributor

@sthompson-queue something has gone wrong with your pr. There is more than 5k files changes..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: Apps (W1) Add-on apps for W1 Build: Automation Workflows and other setup in .github folder Build: scripts & configs Build scripts and configuration files From Fork Pull request is coming from a fork

2 participants