Hello,

I have a question/bug(?) concerning opportunities, products and the
estimated revenue.

For a client of us, we need to default the revenue option to "user provided"
and put the field to "read only" so no total revenue ican automatically
calculated on the opportunity level. THey always need to enter the total
revenue manually.

But if I now add a product from the PriceList to an OpportunityProduct, the
price_per_unit of this product from the PL is not fetched, and no
total_amount is calculated on the Opportunity Product Level.

If I now re-open the Opportunity Product, I/the_user sees the error message
on top of the screen:
"The following error occured: An error occurred during pricing of a detail
line item."

Results:
Product: x ... Unit: Y
Price per unit = 0,00
Quantity=100
Amount=0,00

I dont think it should be the case that if on Opportunity Level "user
calculated" is provided, that on Opportunity_Product level no total_amounts
are being calculated. Am I correct?

So is this a normal result of my actions, or is there some sort of a bug?

Thanks in advance,

kind regards,
Sebastiaan Dewolf

RE: Opportunity - Opp product / error by RonaldL

RonaldL
Thu Mar 13 07:20:01 CDT 2008

Hi Sebastiaan,

You are changing the value for the revenue option to user provided. The
field is now marked as 'IsDirty'. This would mean that the value for this
will be stored to the database. But, you are also setting the field as
readonly. This indicates to crm that the field cannot be modified, which
means that the saving procedure will skip this field when looking to the
IsDirty flags. You will need to specify on the field that it needs to be
stored to the database. You can do this by setting the attributes property
'ForceSubmit' to true. You'll find information about that in the SDK.

With kind regards
--
Ronald Lemmen - MSCRM MVP
Avanade Netherlands
http://www.ronaldlemmen.com/


"sebastiaan dewolf" wrote:

> Hello,
>
> I have a question/bug(?) concerning opportunities, products and the
> estimated revenue.
>
> For a client of us, we need to default the revenue option to "user provided"
> and put the field to "read only" so no total revenue ican automatically
> calculated on the opportunity level. THey always need to enter the total
> revenue manually.
>
> But if I now add a product from the PriceList to an OpportunityProduct, the
> price_per_unit of this product from the PL is not fetched, and no
> total_amount is calculated on the Opportunity Product Level.
>
> If I now re-open the Opportunity Product, I/the_user sees the error message
> on top of the screen:
> "The following error occured: An error occurred during pricing of a detail
> line item."
>
> Results:
> Product: x ... Unit: Y
> Price per unit = 0,00
> Quantity=100
> Amount=0,00
>
> I dont think it should be the case that if on Opportunity Level "user
> calculated" is provided, that on Opportunity_Product level no total_amounts
> are being calculated. Am I correct?
>
> So is this a normal result of my actions, or is there some sort of a bug?
>
> Thanks in advance,
>
> kind regards,
> Sebastiaan Dewolf

RE: Opportunity - Opp product / error by sebastiaandewolf

sebastiaandewolf
Wed Mar 19 03:01:01 CDT 2008

Bedankt Ronald,

I tried your comment with this operation in the Onload event of the
Opportunity:
var oField = crmForm.all. isrevenuesystemcalculated;
oField.ForceSubmit = true;

Unfortunately, it changed nothing... The error on Opportunity_Products is
still there, no price_per_unit is fetched from the price_list.

Do you have any other possible solutions?

thanks in advance
Sebastiaan

"Ronald Lemmen" wrote:

> Hi Sebastiaan,
>
> You are changing the value for the revenue option to user provided. The
> field is now marked as 'IsDirty'. This would mean that the value for this
> will be stored to the database. But, you are also setting the field as
> readonly. This indicates to crm that the field cannot be modified, which
> means that the saving procedure will skip this field when looking to the
> IsDirty flags. You will need to specify on the field that it needs to be
> stored to the database. You can do this by setting the attributes property
> 'ForceSubmit' to true. You'll find information about that in the SDK.
>
> With kind regards
> --
> Ronald Lemmen - MSCRM MVP
> Avanade Netherlands
> http://www.ronaldlemmen.com/
>
>
> "sebastiaan dewolf" wrote:
>
> > Hello,
> >
> > I have a question/bug(?) concerning opportunities, products and the
> > estimated revenue.
> >
> > For a client of us, we need to default the revenue option to "user provided"
> > and put the field to "read only" so no total revenue ican automatically
> > calculated on the opportunity level. THey always need to enter the total
> > revenue manually.
> >
> > But if I now add a product from the PriceList to an OpportunityProduct, the
> > price_per_unit of this product from the PL is not fetched, and no
> > total_amount is calculated on the Opportunity Product Level.
> >
> > If I now re-open the Opportunity Product, I/the_user sees the error message
> > on top of the screen:
> > "The following error occured: An error occurred during pricing of a detail
> > line item."
> >
> > Results:
> > Product: x ... Unit: Y
> > Price per unit = 0,00
> > Quantity=100
> > Amount=0,00
> >
> > I dont think it should be the case that if on Opportunity Level "user
> > calculated" is provided, that on Opportunity_Product level no total_amounts
> > are being calculated. Am I correct?
> >
> > So is this a normal result of my actions, or is there some sort of a bug?
> >
> > Thanks in advance,
> >
> > kind regards,
> > Sebastiaan Dewolf

RE: Opportunity - Opp product / error by sebastiaandewolf

sebastiaandewolf
Mon Apr 07 08:17:02 CDT 2008

Ronald, did you have time to look into this a bit further?

Does anybody else perhaps have an idea what could cause the error?

I still get an error when I add a OpportunityProduct to an Opportunity when
the field "Estimated Revenue" on Opportunity level is marked "user provided".
No Opportunity_Product_Price is fetched from the PriceList. I tried this on
multiple setups, same error each time.

kind regards,
Sebastiaan

"Ronald Lemmen" wrote:

> Hi Sebastiaan,
>
> You are changing the value for the revenue option to user provided. The
> field is now marked as 'IsDirty'. This would mean that the value for this
> will be stored to the database. But, you are also setting the field as
> readonly. This indicates to crm that the field cannot be modified, which
> means that the saving procedure will skip this field when looking to the
> IsDirty flags. You will need to specify on the field that it needs to be
> stored to the database. You can do this by setting the attributes property
> 'ForceSubmit' to true. You'll find information about that in the SDK.
>
> With kind regards
> --
> Ronald Lemmen - MSCRM MVP
> Avanade Netherlands
> http://www.ronaldlemmen.com/
>
>
> "sebastiaan dewolf" wrote:
>
> > Hello,
> >
> > I have a question/bug(?) concerning opportunities, products and the
> > estimated revenue.
> >
> > For a client of us, we need to default the revenue option to "user provided"
> > and put the field to "read only" so no total revenue ican automatically
> > calculated on the opportunity level. THey always need to enter the total
> > revenue manually.
> >
> > But if I now add a product from the PriceList to an OpportunityProduct, the
> > price_per_unit of this product from the PL is not fetched, and no
> > total_amount is calculated on the Opportunity Product Level.
> >
> > If I now re-open the Opportunity Product, I/the_user sees the error message
> > on top of the screen:
> > "The following error occured: An error occurred during pricing of a detail
> > line item."
> >
> > Results:
> > Product: x ... Unit: Y
> > Price per unit = 0,00
> > Quantity=100
> > Amount=0,00
> >
> > I dont think it should be the case that if on Opportunity Level "user
> > calculated" is provided, that on Opportunity_Product level no total_amounts
> > are being calculated. Am I correct?
> >
> > So is this a normal result of my actions, or is there some sort of a bug?
> >
> > Thanks in advance,
> >
> > kind regards,
> > Sebastiaan Dewolf