How to handle multiple exceptions(Try..Catch)
-
I have the same thing for prc.Consignee. So what would you suggest something like this:
),
new XElement("PickupStoreInfo",
new XElement("PickupDueDateDetails",
new XElement("Date"),
new XElement("UTCOffset")
),I pretty much have to pass a value in the node or else how else would I get the values?
If you have to pass a value, then pass the value that the API is expecting. Passing the same (invalid) string for each node will most likely cause the API to return an error.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
If you have to pass a value, then pass the value that the API is expecting. Passing the same (invalid) string for each node will most likely cause the API to return an error.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
If you have to pass a value, then pass the value that the API is expecting.
What would that be? Something like:
new XElement("PickupStoreInfo",
new XElement("PickupDueDateDetails",
new XElement("Date", Date),
new XElement("UTCOffset", UTCOffset)
),Not sure???
-
Richard Deeming wrote:
If you have to pass a value, then pass the value that the API is expecting.
What would that be? Something like:
new XElement("PickupStoreInfo",
new XElement("PickupDueDateDetails",
new XElement("Date", Date),
new XElement("UTCOffset", UTCOffset)
),Not sure???
Pass in the values that the API is expecting you to pass in for the request. You've presumably read the API documentation? The expected values should be documented there.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Pass in the values that the API is expecting you to pass in for the request. You've presumably read the API documentation? The expected values should be documented there.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Yes i've read it and if that is the case then the values in the API are the same as the XElement so Here the a piece of the API schema:
Event Status
I guess it will look like this?
new XElement("EventStatus", "Event Status"), ), -
Yes i've read it and if that is the case then the values in the API are the same as the XElement so Here the a piece of the API schema:
Event Status
I guess it will look like this?
new XElement("EventStatus", "Event Status"), ),Bootzilla33 wrote:
Here the a piece of the API schema:
<xsd:element
name="EventStatus" type="xsd:string">
xsd:annotation\
xsd:documentation\Event Status</xsd:documentation>
</xsd:annotation>
</xsd:element>I guess it will look like this?
new XElement("EventStatus", "Event Status"),),
Just need help with this and I think I'm done.
-
Bootzilla33 wrote:
Here the a piece of the API schema:
<xsd:element
name="EventStatus" type="xsd:string">
xsd:annotation\
xsd:documentation\Event Status</xsd:documentation>
</xsd:annotation>
</xsd:element>I guess it will look like this?
new XElement("EventStatus", "Event Status"),),
Just need help with this and I think I'm done.
Someone please help me with this. I would greatly appreciate it. Thanks
