-
Notifications
You must be signed in to change notification settings - Fork 15
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
Unable to list or create a shippinglabel #64
Comments
@Coffee-19, do you have the latest release 1.2024.911.1? |
Hi @Ben-Carpenter, |
Okay, thanks for the info, we will take a look at see what we can find. |
@Ben-Carpenter I encountered the same issue using 1.2024.911.1. Here is my exception log: **SurfaceDevCenterManager v1.0.0.1
============================================================
|
Thank you for your reply and comments. This is on our backlog to check out. Were you able to find a workaround in the meantime? |
@Ben-Carpenter No. I couldn't find a workaround. |
@SenaryNick , sorry to hear. Please see comment from Coffee-19 on Nov 12, 2024 in this thread.
|
Hi SDCM team,
I encountered an issue while using the latest SDCM to list or create a shipping label.
Here is the SDCM exception log.
============================================================
SurfaceDevCenterManager Exception Log
Option: ListOption
Section: GetShippingLabels
Type: System.Text.Json.JsonException
Message: The JSON value could not be converted to System.String. Path: $.value[0].publishingSpecifications.visibleToAccounts[0] | LineNumber: 0 | BytePositionInLine: 196.
Inner Exception: Cannot get the value of a token type 'Number' as a string.
Correlation Id: cf5b4e6f-b686-4d21-9176-bdda9cdf0158
To Reproduce
SDCM -list shippinglabel -productid pid -submissionid sid -shippinglabelid slid
or
SDCM -create create_shippinglabel.json -productid pid -submissionid sid
Expected behavior
List a shipping label information or create a shipping label on the partner center
Desktop (please complete the following information)
The text was updated successfully, but these errors were encountered: