-
Notifications
You must be signed in to change notification settings - Fork 26
Label Generation for (non-standard) Packages #67
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
Comments
Can you share the traceback? |
Please pardon my ignorance, but I'm not even sure how to get that. I am accustomed to having a "copy to clipboard" button in frappe, and I can't find anything in the frappe error logs. |
Try the browser console for a traceback first, if there isn't one there, look in ~/frappe-bench/logs/web.error.log |
Oh, yes, I "knew" that... here's the traceback from both errors:
|
When using the 'Package' package, I think it's expecting dimensional information, for which an input is not provided in the UI. |
Looking at the docs, it seems like Either way, it seems like Side-note: @agritheory, it seems like the client is reporting 500 errors for both of these, even though the |
In my client's scenario, we have several box sizes he uses that I'd like to make available in a drop-down link. Is there a pre-existing doctype available for this (I'm not seeing any), or would it make sense to build this into this integration, perhaps as a dedicated "Shipstation Custom Package" doctype? |
I'm getting "Object reference not set to an instance of an object." and "Invalid packageCode" when trying to generate labels:

How can I diagnose what's going on here?
The text was updated successfully, but these errors were encountered: