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

LSR-13378: Custom Template for Purchase Order is not displaying the correct Vendor ID #70

Merged

Conversation

ls-lindsay-powerharding
Copy link
Contributor

@ls-lindsay-powerharding ls-lindsay-powerharding commented Dec 8, 2021

Previously, the first vendor ID in the list would be chosen, now the vendor ID that matches the PO vendor will print, else the field will be blank.

Copy link

@ls-robert-bowes ls-robert-bowes left a comment

Choose a reason for hiding this comment

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

👍

Copy link

@tombertrand tombertrand left a comment

Choose a reason for hiding this comment

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

🌮

@ls-lindsay-powerharding ls-lindsay-powerharding merged commit 1873c6a into master Dec 9, 2021
@urbanangler
Copy link

You guys didn't address the vendor cost associated with the vendor ID.

@ls-lindsay-powerharding
Copy link
Contributor Author

You guys didn't address the vendor cost associated with the vendor ID.

We weren't aware there was an issue there, if you could send me a slack message with the details we can create a Jira card to look into it.

@urbanangler
Copy link

urbanangler commented Dec 10, 2021 via email

@urbanangler
Copy link

Do you have an email I can send a slack message to?

@ls-lindsay-powerharding
Copy link
Contributor Author

Do you have an email I can send a slack message to?

Hello! You can reach out to the Lightspeed Support team and they will document your request and submit to us and you will receive updates as they are available, or alternatively if you wanted to provide details here I can create a task for the team to review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants