feat: Add new tables, pages, and extensions for Avalara integration #6391
+4,926
−206
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Created "AvalaraInput Field" table to store input field configurations. - Added "Avalara Input Fields" page for managing input fields. - Extended "Posted Sales Credit Memo" page to include Avalara Doc. ID. - Extended "Sales Cr.Memo Header" and "Sales Header" tables to include Avalara Doc. ID. - Added "Avalara Trans. Rule Type" enum extension for Avalara-specific transformation rules. - Extended "Data Exch Field Mapping Part" page to include default value field. - Enhanced "E-Doc. Service Data Exch. Sub" page with assist edit for document type. - Extended "E-Documents" page with actions for receiving and downloading documents from Avalara. - Created "Maintenance" codeunit for processing E-Documents. - Added "Media Types" and "Message Event" tables for handling media types and message events. - Created "Message Events Subform" and "Message Response Card" pages for displaying message events and responses. - Extended "Transformation Rule" table to include advanced lookup fields. - Updated "Transformation Rules" page to support advanced lookup configuration.
github-actions
bot
added
AL: Apps (W1)
Contributor
|
@sthompson-queue i want it build, before the PG does any review. Then for the review part, i would ask for technical documentation on the app. You can add it as a readme.MD file in the project root, or on the PR itself. I would also ask you to write tests both E2E and unit tests. |
Groenbech96
requested changes
Feb 3, 2026
Contributor
Groenbech96
left a comment
Groenbech96
left a comment
There was a problem hiding this comment.
Currently not building
- Added namespace and using directives for Avalara integration across multiple files. - Extended various pages and tables to support Avalara-specific functionality, including Sales Credit Memo, Sales Header, and Message Event. - Enhanced Connection Setup Card with improved tooltips and updated variable names for clarity. - Introduced new fields and improved data handling in the Message Response and Message Event tables. - Updated Processing and Requests codeunits to streamline document handling and API interactions. - Created README.md for comprehensive documentation on the Avalara E-Document Connector, detailing architecture, setup, and usage.
Author
|
@Groenbech96 I have modified the code to align with the MS rulesets and have added a readme.md. I am working on the integration tests now. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Enhancements for the setup and processing experience by adding:
(1) a Test Connection button in setup
(2) dynamic input fields driven by country mandates
(3) download and update of tax-authority-returned invoice documents
(4) response status management per invoice
(5) receive notifications from Avalara ELR
Work Item(s)
Fixes #6385