Customized BO Blank Title 107083

Yahoo Archive
1
John wrote:
>
> Add all the configurator dlls. There should be 3 in all --AD,BO and IF.
>

Yeah, that's what I do in my .Net programs and it looked like it they were in there but I added it again and only two said they were only there. All set. Thanks!!!

Mark W.
2
I'm used to calling BOs from .Net programs but would like to have access to one of the BO datasets for an EXISTING BO. In this case, I want to run through the Product Configurator's PCRulesBOMDataSet which is not visible in any EpiDataView but is in the Configurator business object.

Is there a way to grab the open BO for the open form? Not sure if I could get it from the Session object or ConfiguratorForm object or some other way.

Thanks!!!

Mark W.

P.S. What does the "sender" object do? I'm using a button-click event and maybe that could be useful.
3
The easiest way to deal with the 'active BO' is usually to just use the
adapter. Not exactly the same of course, but it should give you access to
all the same functionality.

On Fri, Jan 27, 2012 at 10:10 AM, Mark <mark_wonsil@...> wrote:

> **
>
>
> I'm used to calling BOs from .Net programs but would like to have access
> to one of the BO datasets for an EXISTING BO. In this case, I want to run
> through the Product Configurator's PCRulesBOMDataSet which is not visible
> in any EpiDataView but is in the Configurator business object.
>
> Is there a way to grab the open BO for the open form? Not sure if I could
> get it from the Session object or ConfiguratorForm object or some other way.
>
> Thanks!!!
>
> Mark W.
>
> P.S. What does the "sender" object do? I'm using a button-click event and
> maybe that could be useful.
>
>
>



--
*John Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
4
John wrote:
>
> The easiest way to deal with the 'active BO' is usually to just use the
> adapter. Not exactly the same of course, but it should give you access to
> all the same functionality.

Thanks John. So just update the adapter and then send a notify to update the user interface?

Mark
5
Bingo!

On Fri, Jan 27, 2012 at 11:16 AM, Mark <mark_wonsil@...> wrote:

> **
>
>
> John wrote:
> >
> > The easiest way to deal with the 'active BO' is usually to just use the
> > adapter. Not exactly the same of course, but it should give you access to
> > all the same functionality.
>
> Thanks John. So just update the adapter and then send a notify to update
> the user interface?
>
> Mark
>
>
>



--
*John Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
6
John wrote:
>
> Bingo!
>

Well, almost Bingo...based on examples from others, I start with declaring the adapter

ConfiguratorAdapter adConfig = new ConfiguratorAdapter();

but I'm getting an error:

The type or namespace name: 'ConfiguratorAdapter' could not be found (are you missing a using directive or an addembly reference?)

So I add "using Epicor.Mfg.AD.Configurator;" but I get another error:

The type or namespace name 'AD' does not exist in the namespace 'Epicor.Mfg' (are you missing an assembly reference?

No, I'm missing my mind because when I go to the Custom Asssembly Reference Manager I see that Epivor.Mfg.AD.Configurator is listed.

I've got to be missing something simple here. Any thoughts?

Thanks!!!

Mark W.
7
Add all the configurator dlls. There should be 3 in all --AD,BO and IF.

On Fri, Jan 27, 2012 at 11:56 AM, Mark <mark_wonsil@...> wrote:

> **
>
>
> John wrote:
> >
> > Bingo!
> >
>
> Well, almost Bingo...based on examples from others, I start with declaring
> the adapter
>
> ConfiguratorAdapter adConfig = new ConfiguratorAdapter();
>
> but I'm getting an error:
>
> The type or namespace name: 'ConfiguratorAdapter' could not be found (are
> you missing a using directive or an addembly reference?)
>
> So I add "using Epicor.Mfg.AD.Configurator;" but I get another error:
>
> The type or namespace name 'AD' does not exist in the namespace
> 'Epicor.Mfg' (are you missing an assembly reference?
>
> No, I'm missing my mind because when I go to the Custom Asssembly
> Reference Manager I see that Epivor.Mfg.AD.Configurator is listed.
>
> I've got to be missing something simple here. Any thoughts?
>
> Thanks!!!
>
> Mark W.
>
>
>



--
*John Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]