x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 199 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Proconsult

Oppo_Description not populated in OpportunityProgress table ?

Posted By

Hi,


I'm considering for one of my implementation a workflow rule named "Reopen opportunity" that will be only available when Opportunity is "Closed" AND "Won".

The idea behind that is quite simple to understand if you consider each client as contract. First time you create an opportunity and a quote with quoteitems. When deal is won you close the opportunity and create a contract.

From this approach each additionnal service for this contract is an additional quoteitem. No need to create a new opportunity : just need reopen the won opportunity and to duplicate the latest version of the quote with its original content and only add the additional quoteitems.

Assuming this choice then it raises a few simple problems to solve : among those problems one lead me to what looks like an issue (v7.1.h - release 7.7 French) :

When creating the opportunity, although oppo_description field is required AND exists in OpportunityProgress table, it is not populated in the tracking table of the Oppo record.

How is this possible ? Can I fix this easily without changing the Opportunity screen organization (ie. moving the Description field from OppoDetailScreen to OppoStatusScreen) ?

Thank you for your help and advice. If needed I can provide more explanations...

  • 0

    Hi there,

    I've had a look at this at and I see exactly what you mean. there does seem to be a strange bug there.

    One thing you could try that might get you by for the moment is to add the oppo_description to the status box (by adding it as an action to the primary rule for opportunity) and making it READ ONLY. This will mean that users still enter the description in the normal place on the Detail Screen, but because the description is listed on the status box it will be included on the progress record.

    Sorry this is not a very good workaround as it will look a little strange having the description field read only on the status box, but it might get you by for now.

    Alison.

  • 0

    The only thing I would add to Alison's post is please can you log a case with your local Sage team.

  • 0

    Ok thank you for your answers. I already logged a case (no feedback since 2 weeks but it's usual with french support...).

    I've set up a workaround by moving all the fields from the details block to the status block for all the fields that need to be tracked and I will propose this solution to the end users.

    It's finally just a question of habits, so I presume it will be ok...

*Community Hub is the new name for Sage City