I'm trying to remove the From address on the labels that are produced when a shipment is confirmed, AKA blind shipment label. I found the SOShipmentEntry.ShipPackages() method which seems to attach the label file to the packages on the shipment. Following that code back, I'm not seeing any jump off points to tell the respective carriers' API that the shipment is a "blind shipment" or blank out the return address on the label.
I've tried clearing out a couple of the addresses on the shipment request to the carrier API but, they always come back with a validation error.
Has anybody tried this and can maybe shed some light?
TIA!
The carrier plugin is what retrieves/generates the label and then passes that back to the system.
If the carrier does have an API option to support hiding the address, you could write a customization to add support for it however that most likely would involve writing a new plugin.
I doubt most carriers have API options to hide the from address so your only other option would be to modify the label after it is returned from the carrier which would differ based on what format it was returned in.
Related
When creating Shipments for SOs with Acumatica, it is coming up with an error related to the 'SO Package Detail':
'Box ID' cannot be found in the system
Does anyone have any insight as to why this would occur? I had previously thought it may be due to the Box IDs not being listed under the Carrier used, but this did not resolve the error when I added these under the Carriers. These Box IDs are present within Acumatica. It is possibly related to the UOM, or another variable tied to the Box IDs?
You need to add the Box Id's to the packages tab for the Ship Via Codes in Acumatica.
Log into Acumatica, Navigate to Distribution, then click on Shipments.
Click the Configuration tab and select Ship Via Codes.
Select the Ship Via you are using, and click on the packages tab for the Ship Via.
Add the Box ID's you wish to use with this Ship Via
Save the Ship Via Code record
Sounds like one or more of your Stock Items has an invalid Box ID. Review all the Stock Items on the Sales Order(s) you are attempting to ship and verify they all have valid Box ID's.
How can I customize the Calculate Shipping button (the calculator icon) on Sales Orders under the Shipping tab? I've written my own app using the UPS API and I would like to fire that instead of the native NetSuite shipping calculator. So how can I make the Calculate Shipping button fire my custom code?
Sorry but there is no way to do that via API. You could hack it but probably more trouble than it's worth.
to make your custom calc work:
Associate it with a shipping method (or methods) that have flat rate of $0. If you don't use $0 then NS will re-apply the flate rate charge at various inopportune times.
when something changes trigger the API lookup OR
add a button on the SO form that you can click.
You can also add buttons various other ways with more or less degrees of control. One way is to include an inlinehtml field containing the html for a button and have a script show that when one of your associated methods is selected. I'd back that up with a save page client or before submit user event script to re-calc the value when needed.
When I've done this sort of thing I've made a hash of the shipping address and item ids and quantities and stored that as a body level field. Then you can re-calc the hash in a before submit event and call your API only when the hash has changed.
An another way would be to add a new button using
form.getSublist('item').addButton(name, label, script);
//button would be added in item sublist section
In your script parameter specify the onclick script, the onclick script would be a client side javascript in which you should be able to get SO lines and then fire a AJAX to your suitelet [even nlapiReuqstURL should work smoothly here] which in turn can make calls to your UPS APIs and fetch the rates from there.
Now, the challenge remains is getting rid of the natural calculate shipping button. Probably, you can make it a zero cost one or make the label of new button more appealing to click over the standard one.
I am using embeded signing and I have noticed that the checkbox's are in different locations at different stages.
I can either make it look correct while doing embeded signing... the check mark is centered in the box, or I can make it so that the check marks (X's) are properly centered in the summary pdf.
However I do not know how to consistently get the check marks to align in both the embeded interface, or the pdf summary...
anyone solve this?
This is not the answer you're hoping for but -- unfortunately, there are not separate settings to specify the location of a form field during signing versus on the completed document (PDF). You only get one opportunity to specify a field's location (during the Create Envelope process), and DocuSign then automatically determines location of the field in the completed document (PDF) -- presumably using the same coordinates that you specified during the "Create Envelope" process, although not always exact (as you've discovered with the checkbox element).
So, the best advice I can offer is to always verify placement of fields BOTH in the signing view AND in the completed view -- and then use trial and error to specify field location in a way that produces best overall results across both views.
Our Orchard application displays two of all notifications that are added to the notification service. So far we have traced the problem and know what is causing it, but are looking for a solution other than the obvious, for reasons I shall now elaborate.
So we are using a number of themes to render our Orchard based application. Within our layout, we have a Razor call to draw a header bar that displays a set of information about the user that is logged in.
#Html.Action("OutOfGameHeader", "Options", new { area = "Area.area.Location.Common" })
This action calls the OnResultExecuting() method in Orchard.UI.Notify.NotifyFilter which (among other things) populates the Messages Zone with the current set of notifications. When we make the call the render the Messages Zone, this same method runs again and the notifications are added to the Zone's shape again resulting in duplicate notification being displayed when the Zone is actually drawn.
Can anyone think of a solution that meets the following criteria:
Drawing the header without calling #Html.Action() to avoid OnResultExecuting() being triggered the first time.
Without creating a new Widget in a new Zone as this would involve us changing the manifest for dozens of existing themes to include it.
We also found this just below the point in the code where the notifications are added to the Zone, so if anyone knows anything more about it, that would be helpful too.
//todo: (heskew) probably need to keep duplicate messages from being pushed into the zone like the previous behavior
//baseViewModel.Messages = baseViewModel.Messages == null ? messageEntries .Messages.Union(messageEntries).ToList();
//baseViewModel.Zones.AddRenderPartial("content:before", "Messages", baseViewModel.Messages);
Any thoughts greatly appreciated.
Avoid Html.Action. This runs through the whole lifecycle as if this was a new request. That you think you need it is often a sign that you need to refactor and extract that logic that you want to re-use out of your controller. In Orchard, it's also better to use dynamic shapes.
since the emails loads dynamically how do you find a specific email that contains a button back to your site. This is like signing up at a site. Customer receives email to confirm.
Thanks for the support
BigD
OWA, bless MS's little hearts (at least in the circa 2003 version I'm looking at here) uses frames, so first of all brush up on that or you are gonna be hating life. The list of incoming messages is in a frame named 'viewer' The message summaries are contained in a table lacking any useful means to identify it that is in a div of class 'msgViewerCont" and an ID of dvContents. So to see if a message exists you want to look to see if you can find a row in that table which contains the subject you expect to see.
(be careful using ID values on OWA.. apparently nobody in the group that developed it read the part of the HTML standard that specifies that ID values are supposed to be unique.. the re-use them all over that page.)
Presuming you know the subject of the message you are about to receive, and also that you keep that mail account cleared out so that it will be the ONLY message there with that subject line, then you can check to see if it exists usng
subject = regex.new("subject you are looking for")
browser.frame(:name, 'viewer').div(:id, dvContents).table(:index, 1).row(:text, subject).exists?
to click on it use .click instead of exists.
once you've clicked it, OWA will refresh the PreviewPane iframe.. inside that iframe is another one that has the message body in it.
all those frames, are nested inside the viewer frame. welcome to nested frame hell. hope you enjoy your stay. (like I said, bone up on frames, you're in for a fun ride)