oui and acnt screen

Hello merchant-coders,

Writing a custom OUI module. I'm adding a couple fields to the
Customer Add/Edit screen (ACNT) which will be stored in a separate
db so I don't have to screw with native dbs. The problem I having is
that I can't any of this new data to saved. I've tried a savedata
function in a system module and a logging module. For instance, in
the system module, I was thinking that savedata function would
reside in:

<MvFUNCTION NAME = "SystemModule_Action_Customer_Update">

The function does not seem to run, or at least the code inside. I've
tried just simple MvExport stuff.

So, I've been kind stumped here. Any ideas? TIA.

fyi: this extra data will be stored in a independant db along with
the cust_id and maybe a couple other fields. It will be a required
field for customers who are new or who already exist.

--
Best regards,
Scott
mailto:[email protected]

oui and acnt screen



I haven't rec'd any response on the OPENUI forum either. Anybody have
any ideas where I could avoid adding code to the OUI scripts and/or
changing the native dbs?

I did have another thought about using hookpoints. I don't know what
submodule from though. The ACNT screen is in 'oui_scae' submodule. I
can't seem to find what function stores the new or updated data.

TIA,

Scott
IDS

Wednesday, March 2, 2005, 2:42:43 PM, you wrote:

SS> Hello merchant-coders,

SS> Writing a custom OUI module. I'm adding a couple fields to the
SS> Customer Add/Edit screen (ACNT) which will be stored in a separate
SS> db so I don't have to screw with native dbs. The problem I having is
SS> that I can't any of this new data to saved. I've tried a savedata
SS> function in a system module and a logging module. For instance, in
SS> the system module, I was thinking that savedata function would
SS> reside in:

SS> <MvFUNCTION NAME = "SystemModule_Action_Customer_Update">

SS> The function does not seem to run, or at least the code inside. I've
SS> tried just simple MvExport stuff.

SS> So, I've been kind stumped here. Any ideas? TIA.

SS> fyi: this extra data will be stored in a independant db along with
SS> the cust_id and maybe a couple other fields. It will be a required
SS> field for customers who are new or who already exist.




--
Best regards,
Scott
mailto:[email protected]

oui and acnt screen



Dear Scott,

You probably need to interrupt the normal system flow and use:

<MvFUNCTION NAME = "SystemModule_Action_New" STANDARDOUTPUTLEVEL = "text">

To save the data.

Thank you,

Nerd Boy

1-573-292-1136
<A HREF ="http://www.nerdboyinc.com">http://www.nerdboyinc.com</A>
<A HREF ="http://www.nbicentral.com">http://www.nbicentral.com</A>
<A HREF ="http://www.crosstowntraffic.net">http://www.crosstowntraffic.net</A>
Your alternative source for Miva Merchant Modules

For Customer Service and Support:
http://support.nerdboyinc.com
or send email to: [email protected]

<A HREF ="http://www.nerdboyproductions.com">http://www.nerdboyproductions.com</A>
<A HREF ="http://www.asmallurl.com">http://www.asmallurl.com</A>
<A HREF ="http://www.nbiracing.com">http://www.nbiracing.com</A>
<A HREF ="http://www.yourlottosite.com">http://www.yourlottosite.com</A>

----- Original Message -----
From: "Scott Shepard" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 03, 2005 12:32 PM
Subject: Re: [mrc] oui and acnt screen


>I haven't rec'd any response on the OPENUI forum either. Anybody have
> any ideas where I could avoid adding code to the OUI scripts and/or
> changing the native dbs?
>
> I did have another thought about using hookpoints. I don't know what
> submodule from though. The ACNT screen is in 'oui_scae' submodule. I
> can't seem to find what function stores the new or updated data.
>
> TIA,
>
> Scott
> IDS
>
> Wednesday, March 2, 2005, 2:42:43 PM, you wrote:
>
> SS> Hello merchant-coders,
>
> SS> Writing a custom OUI module. I'm adding a couple fields to the
> SS> Customer Add/Edit screen (ACNT) which will be stored in a separate
> SS> db so I don't have to screw with native dbs. The problem I having is
> SS> that I can't any of this new data to saved. I've tried a savedata
> SS> function in a system module and a logging module. For instance, in
> SS> the system module, I was thinking that savedata function would
> SS> reside in:
>
> SS> <MvFUNCTION NAME = "SystemModule_Action_Customer_Update">
>
> SS> The function does not seem to run, or at least the code inside. I've
> SS> tried just simple MvExport stuff.
>
> SS> So, I've been kind stumped here. Any ideas? TIA.
>
> SS> fyi: this extra data will be stored in a independant db along with
> SS> the cust_id and maybe a couple other fields. It will be a required
> SS> field for customers who are new or who already exist.
>
>
>
>
> --
> Best regards,
> Scott
> mailto:[email protected]
>
>
>

oui and acnt screen




From your description, you seem to be on the right track. Note that a
system extension module's Action_Customer_Update function will be called
before the Miva databases are written, while a logging module's function
will be called after. This means that the log module will not be called if
the action fails, e.g. if the user forgot to fill in a required
field. Also note that there are Customer_Insert actions in both kinds of
modules, since creating a new customer is distinct from updating an
existing one.

I'd recommend the log module. Make sure you call your savedata function
from both the Customer_Insert and Customer_Update functions. Put some
MvEVAL statements at the start of the Miva functions to display an "I got
here" message, along with the value from one or two of your input
fields. The messages should show up right at the top of the screen, since
Merchant handles all the action functions before it starts drawing the
screen. If the messages don't show up, there must be something else wrong
with your module (e.g. wrong module_type), or with how you installed it
(e.g. forgot to assign it to the store in System Ext. or Logging
Configuration).

Hope that helps --


>Hello merchant-coders,
>
> Writing a custom OUI module. I'm adding a couple fields to the
> Customer Add/Edit screen (ACNT) which will be stored in a separate
> db so I don't have to screw with native dbs. The problem I having is
> that I can't any of this new data to saved. I've tried a savedata
> function in a system module and a logging module. For instance, in
> the system module, I was thinking that savedata function would
> reside in:
>
> <MvFUNCTION NAME = "SystemModule_Action_Customer_Update">
>
> The function does not seem to run, or at least the code inside. I've
> tried just simple MvExport stuff.
>
> So, I've been kind stumped here. Any ideas? TIA.
>
> fyi: this extra data will be stored in a independant db along with
> the cust_id and maybe a couple other fields. It will be a required
> field for customers who are new or who already exist.
>
>--
>Best regards,
> Scott
>mailto:[email protected]




Kent Multer | /| P.O.Box 701895, Dallas TX 75370
Magic Metal Productions | / | (214) 570 8264 voice/fax
| | [email protected]
* Web developer/designer http://TheMagicM.com
* E-commerce and Miva
* Author, The Official Miva Web Scripting Book -- available on-line:
<A HREF ="http://www.amazon.com/exec/obidos/ISBN=0966103211/magicmetalproducA">http://www.amazon.com/exec/obidos/ISBN=0966103211/magicmetalproducA</A>

another suggestion if needed please



Thanks everybody that weighed in. I am going with the logging module
solution. The system module was actually working. Seems I had some
unsightly characters in my code that rendered my test code worthless
giving me a false-fail condition. Just gotta be careful when
copy/pasting old code.

So my question, since using a log module to record my new fields, is
there any OUI_ext I need to create that will make the code kosher to
OUI, since this is an OUI installed store? Every thing I've looked at
doesn't tell me that system mods or logging mods need to be treated
differently than an MMUI type module just because its an OUI store.

TIA again,

Scott
IDS

Thursday, March 3, 2005, 7:26:20 PM, you wrote:


K> From your description, you seem to be on the right track. Note that a
K> system extension module's Action_Customer_Update function will be called
K> before the Miva databases are written, while a logging module's function
K> will be called after. This means that the log module will not be called if
K> the action fails, e.g. if the user forgot to fill in a required
K> field. Also note that there are Customer_Insert actions in both kinds of
K> modules, since creating a new customer is distinct from updating an
K> existing one.

K> I'd recommend the log module. Make sure you call your savedata function
K> from both the Customer_Insert and Customer_Update functions. Put some
K> MvEVAL statements at the start of the Miva functions to display an "I got
K> here" message, along with the value from one or two of your input
K> fields. The messages should show up right at the top of the screen, since
K> Merchant handles all the action functions before it starts drawing the
K> screen. If the messages don't show up, there must be something else wrong
K> with your module (e.g. wrong module_type), or with how you installed it
K> (e.g. forgot to assign it to the store in System Ext. or Logging
K> Configuration).

K> Hope that helps --


>>Hello merchant-coders,
>>
>> Writing a custom OUI module. I'm adding a couple fields to the
>> Customer Add/Edit screen (ACNT) which will be stored in a separate
>> db so I don't have to screw with native dbs. The problem I having is
>> that I can't any of this new data to saved. I've tried a savedata
>> function in a system module and a logging module. For instance, in
>> the system module, I was thinking that savedata function would
>> reside in:
>>
>> <MvFUNCTION NAME = "SystemModule_Action_Customer_Update">
>>
>> The function does not seem to run, or at least the code inside. I've
>> tried just simple MvExport stuff.
>>
>> So, I've been kind stumped here. Any ideas? TIA.
>>
>> fyi: this extra data will be stored in a independant db along with
>> the cust_id and maybe a couple other fields. It will be a required
>> field for customers who are new or who already exist.
>>
>>--
>>Best regards,
>> Scott
>>mailto:[email protected]


--
Best regards,
Scott
mailto:[email protected]

another suggestion if needed please




OpenUI hooks are mostly just for altering the appearance of the
screen. OUI doesn't get involved in the "Action" processing, which is done
before Merchant starts drawing the screen. So, yes, if your module is just
saving data when its _Action_ functions get called, then it will work in
OUI or MMUI stores.


>Thanks everybody that weighed in. I am going with the logging module
>solution. The system module was actually working. Seems I had some
>unsightly characters in my code that rendered my test code worthless
>giving me a false-fail condition. Just gotta be careful when
>copy/pasting old code.
>
>So my question, since using a log module to record my new fields, is
>there any OUI_ext I need to create that will make the code kosher to
>OUI, since this is an OUI installed store? Every thing I've looked at
>doesn't tell me that system mods or logging mods need to be treated
>differently than an MMUI type module just because its an OUI store.
>
>TIA again,
>
>Scott
>IDS




Kent Multer | /| P.O.Box 701895, Dallas TX 75370
Magic Metal Productions | / | (214) 570 8264 voice/fax
| | [email protected]
* Web developer/designer http://TheMagicM.com
* E-commerce and Miva
* Author, The Official Miva Web Scripting Book -- available on-line:
<A HREF ="http://www.amazon.com/exec/obidos/ISBN=0966103211/magicmetalproducA">http://www.amazon.com/exec/obidos/ISBN=0966103211/magicmetalproducA</A>