|
Posted by SalaMarv on June 20, 2007, 8:25 pm
Please log in for more thread options I was wondering about that, since the field is greyed out. Thanks for
clearing that up.
Client had setup all emps as local custs across all stores range ID 20 to
100.
Needed to switch to global and retain the local history,
so SQL'd the local custs to addin a 99 before the ID and a ZZ in front of
first/last name.
No merge into one global since that info is "CustomerSource" bla...
Setup Globals in the 500 range and deployed these to stores.
Nice to know i can update the 500 range -500 to retain the original numbers
for ease of use.
Added Globals, was
"Afshin Alikhani" wrote:
> The accountnumber can be changed. This is the query.
>
> Update Customer Set AccountNumber = 'ABC' , LastUpdated = GetDAte() Where
> AccountNumber = 'XYZ'
>
> This will change the last updated date of the customer record and on the
> next WS401 connection the information will go up to the stores
>
> Afshin Alikhani - [ afshin@retailrealm.co.uk ]
> CEO - Retail Realm
> = = = = = = = = = = = = = =
>
> > Hi,
> >
> > I want to change the Global Customer Account Numbers for some of my
> > customers in SQL. I know how to do it since I'm a SQL guy ... But since
> > it's
> > grayed out on the GUI I'm wondering if this is safe to do. Everything
> > things
> > to run around the HQID and not the AccountNumber field in the Customer
> > table.
> > Is this okay to do with no consequences?
> >
> > Thank you,
> >
> > Bradley
>
>
>
|