Home › Forums › PrintNode Connector › Unable to use different PrintNode accounts in different Companies
Peter JørgensenSeptember 29, 2021 at 7:06 amPost count: 9
My customer have been using PrintNode in several companies in BC with the same PrintNode account (same API Key) without any problems. Now they have started a new company that will use its own PrintNode account with a different set of printers. This gives them a problem with your extension.
When they use the “Get the PrintNode Printers” it deletes the Printer Selections for printers not available in the current company. This is a huge problem, because the Printer Selection table in BC is shared between all companies in the BC instance.
Please either stop deleting Printer Selections with unknown printers, or ask the user if the Printer Selections should be deleted. (And please add a warning, informing the user the Printer Selection is shared for all companies)
Thank you.Brett MacDonellSeptember 29, 2021 at 7:25 amPost count: 37
Hello. Once you have PrintNode set up in one instance, regardless of the company, use the “Update PrintNode Printer” button on either the Insight Works PrintNode Setup or Insight Works PrintNode Printers pages instead of the Load/Reload printer button. Updating new printers will only update new printers, not erase existing printers.
Peter JørgensenSeptember 30, 2021 at 12:05 amPost count: 9
- This reply was modified 1 year, 6 months ago by Brett MacDonell.
Where do I find the “Update PrintNode Printer” button? I only have an PrintNodeSetup -> “Get PrintNode Printers” and no actions on my PrintNodePrinters page. We are using version 2.2.7612.0
However, we would really like a way to prevent accidental deletion of Printer Selections in other companies as it is causing a lot of frustration at my customer.Peter JørgensenOctober 15, 2021 at 2:41 pmPost count: 9
Please let me know if you plan to change this or not.
Currently I have temporarily removed the button from all role centers to prevent accidental deletion. If you don’t see it as a problem, I will have to make a new extension to handle this issue.
- You must be logged in to reply to this topic.