Thread: Excluding USPS First Class Package International Service

The US Post Office has added a shipping service that we would like excluded from the chipping choices presented to our international customers: First-Class Package International Service™**.

We have tried everything to exclude this service in the shipping methods app config: using the hyphen, not using the hyphen, using the TM mark at the end, not using the TM mark......

Has anyone been able to exclude this method? If so, what exactly did you input in the app config to make it happen?

Thank you.

i'm having the same problem and also difficulty preventing the STANDARD POST method. Any help would be appreciated. I've tried prepending the method with "U.S Postal" without success.

I was able to remove Standard Post by typing it exactly that way in the 'shipping methods to prevent' app config. Just type in Standard Post and you shouldn't see it anymore.

The other one I have not been able to remove - still need a solution for that one.

Have you tried to prepend “U.S. Postal” to the method name.
http://manual.aspdotnetstorefront.co...g-methods.aspx

C#/VB.NET Code:

U.S. Postal First-Class Package International Service<sup>™</sup>** 


Using the code you provided works - thank you!

thats really awesome code it has really worked a lot for us

Visit here.. http://www.prlog.org/12114868-lenswo...o-grab-it.html

I keep using this code
U.S. Postal First-Class Package International Service<sup>™</sup>**
and it works for sometime but then stops working and when I go back to the app config it changed from the above to
U.S. Postal First-Class Package International Service<sup>

This has happened several times, anyone know why that could be?

Thanks

Most likely the field that holds that value is getting maxed out. No sure what it limit is, but it will truncate anything over a certain amount of characters after you update. In your case its cutting off the last 25 characters (+/-)

Good thinking, however it works for sometime which tells me that is not the case.

Actually that is exactly the case. The AppConfig value will not get curtailed after you entered the data yet until the cache is reset.

You can expand the Config Value with this set of queries:

1)

Alter Table AppConfig Alter Column ConfigValue Nvarchar(2000)

2)

drop proc [dbo].[aspdnsf_updAppconfig]

3)

create proc dbo.aspdnsf_updAppconfig
@AppConfigID int,
@Description ntext = null,
@ConfigValue nvarchar(2000) = null,
@GroupName nvarchar(100) = null,
@SuperOnly tinyint = null,
@StoreID int = null,
@ValueType nvarchar(100) = null,
@AllowableValues nvarchar(max) = null

AS
SET NOCOUNT ON


UPDATE dbo.Appconfig
SET
Description = COALESCE(@Description, Description),
ConfigValue = COALESCE(@ConfigValue, ConfigValue),
GroupName = COALESCE(@GroupName, GroupName),
SuperOnly = COALESCE(@SuperOnly, SuperOnly),
StoreID = COALESCE(@StoreID, StoreID),
ValueType = COALESCE(@ValueType, ValueType),
AllowableValues = COALESCE(@AllowableValues, AllowableValues)
WHERE AppConfigID = @AppConfigID

Ah I had forgot about the cache. Thanks!