Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[E-Document Connector] SignUp E-Document Connector #27261

Open
wants to merge 37 commits into
base: main
Choose a base branch
from

Conversation

geschwint
Copy link

@geschwint geschwint commented Sep 16, 2024

E-Documents connector interface implementation between Business Central and SignUp Web API for electronic invoices

Work Item(s)
Fixes #27054
Fixes AB#541805

@github-actions github-actions bot added the linked Issue is linked to a Azure Boards work item label Sep 16, 2024
@geschwint
Copy link
Author

@aholstrup1 This pull request has replaced #27084 due to using merge instead of rebase policy locally. Thank you for your patience

@geschwint geschwint marked this pull request as ready for review September 16, 2024 08:16
@JesperSchulz JesperSchulz added the Integration GitHub request for Integration area label Sep 16, 2024
@geschwint
Copy link
Author

geschwint commented Sep 24, 2024

Comment on last commit. Resolving object name conflict in module. Can't have two objects with the same name in the same module even if they are in different namespaces. Ref: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-namespaces-overview

Error in build: https://github.com/microsoft/ALAppExtensions/actions/runs/10956384133/job/30482980067?pr=27261

@Groenbech96
Copy link

Comment on last commit. Resolving object name conflict in module. Can't have two objects with the same name in the same module even if they are in different namespaces. Ref: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-namespaces-overview

Error in build: https://github.com/microsoft/ALAppExtensions/actions/runs/10956384133/job/30482980067?pr=27261

Yep i was looking at this issue as well yesterday. Can you find me and ping me on the E-Doc Open Source teams channel?

@geschwint geschwint requested a review from a team as a code owner September 25, 2024 11:03
@geschwint
Copy link
Author

Latest batch of updates, no changes in logic. Refactoring done to follow structure of incoming Avalara relocation.

@geschwint
Copy link
Author

Build process fails as required field "Service Participant Id" is missing on the table Customer. Build depends on other pull request to complete.

Copy link

@Groenbech96 Groenbech96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of comments and some questions for me to understand the code better. Do you have API doc reference you can link me?

JsonManagement.GetArrayPropertyValueAsStringByName('status', Value);

if Value in ['Sent'] then begin
GetReadyStatus.ScheduleEDocumentJob(Codeunit::GetReadyStatus, BlankRecordId, 120000);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of things:

  1. Dont schedule jobs from a function called "HasSomething". It should check a state.
  2. Question @geschwint What is the flow here? Why cant you rely on the GetResponse job queue job to run?
    • Want to understand the logic here.

@geschwint
Copy link
Author

Couple of comments and some questions for me to understand the code better. Do you have API doc reference you can link me?

Here is the link to the API: https://edoc.exflowdev.cloud/swagger/index.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration GitHub request for Integration area linked Issue is linked to a Azure Boards work item
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BC Idea]: Enable connector with SignUp for E-Documents
3 participants