Change default value for Create Quote dropdown in Opportunities screen

Hi ​@AndrewA ,
Modify you DAC field on screen level .
 

Key changes made:

1. Replaced PXUnboundDefault with PXDefault which has stronger precedence
2. Added PersistingCheck = PXPersistingCheck.Nothing to ensure no validation errors
    

namespace PX.Objects.CR
{
  public class OpportunityMaint_Extension : PXGraphExtension<PX.Objects.CR.OpportunityMaint>
  {
    #region Event Handlers
    
    
    [PXString(1, IsFixed = true)]
                [PXUIField(DisplayName = "Quote Type")]
                [CRQuoteType()]
              [PXDefault(CRQuoteTypeAttribute.Project, PersistingCheck = PXPersistingCheck.Nothing)]
    protected virtual void CreateQuotesFilter_QuoteType_CacheAttached(PXCache cache)
    {
    
    }
    Option 2:
If this still doesn't work, we could try an alternative approach using the RowSelected event:

   namespace PX.Objects.CR
{
    public class OpportunityMaint_Extension : PXGraphExtension<PX.Objects.CR.OpportunityMaint>
    {
        protected virtual void CreateQuotesFilter_RowSelected(PXCache cache, PXRowSelectedEventArgs e)
        {
            if (e.Row is CreateQuotesFilter row && string.IsNullOrEmpty(row.QuoteType))
            {
                row.QuoteType = CRQuoteTypeAttribute.Project;
                cache.IsDirty = false;
            }
        }
    }
}
Hope it will work.

Hi ​

@AndrewA ,

You can try this in Graph

protected void _(Events.RowSelected<CreateQuotesFilter> e)

{

    CreateQuotesFilter quote = e.Row as CreateQuotesFilter;

    if (quote == null) return;

    quote.QuoteType = CRQuoteTypeAttribute.Project;

}
 

Hope this code is helps for you 🤔

Yes, this is possible and would be easy for a developer.

Here’s how I would do it:

[PXMergeAttributes(Method = MergeMethod.Append)]
[PXCustomizeBaseAttribute(typeof(PXUnboundDefaultAttribute), null, CRQuoteTypeAttribute.Project)]
protected virtual void _(Events.CacheAttached<CreateQuotesFilter.quoteType> e) { }

Thanks everyone for your responses. I went with ​@Dipak Nilkanth 's answer, which worked perfectly. I haven't used this fields section much, so it was great to see it in action, and will be handy to use for similar issues in the future.

Kind regards,

Andrew