RE: Workflow Rule Failing in 3.0 by Marc
Marc
Fri Mar 14 03:38:01 CDT 2008
You should do the following:
1. Turn off tracing
2. Delete all trace files
3. Switch tracing back on.
4. Perform an action which will trigger the workflow.
5. Check the logfiles generated, check particularly the crmservice logfile,
there should be an error in there regarding the "no attribute" error.
You can use the trace log viewer from Michael Hoehne (www.stunnware.com) for
easier reading.
Cheers,
Marc
"MD" wrote:
> I did a trace using the CrmDiagToolTurbo and ran through the Sales Process.
> The Log file just for the workflow side is very very long. I have no idea
> what I should be looking for...
> --
> MD
>
>
>
> "Marc" wrote:
>
> > Hey,
> >
> > Can you turn on tracing, reproduce the error and check the trace log to see
> > what the exact error message is?
> >
> > Cheers,
> >
> > Marc
> >
> > "MD" wrote:
> >
> > > Hey,
> > >
> > > So I'm not sure why this "Create" WF rule keeps failing, but I have a
> > > picklist in a task that is set by the WF rule, based on entity conditions. If
> > > the conditions are met the Picklist is set to "Yes" (the picklist has 3
> > > values, "Yes", "No", and "N/A").
> > >
> > > I have some OnLoad code that checks this value, and if the Value is "Yes", a
> > > function that captures the Click "Save As Complete" event throws an Alert and
> > > prevents the action.
> > >
> > > Thing is, the Workflow rule doesn't set the field and if I go to the
> > > Workflow Monitor, I see this error:
> > >
> > > Update: [My Field] = Yes | [Date/Time] | Fail | Error code: 80041103. Query
> > > Builder Error. No Attribute.
> > >
> > > I have not altered/added/removed any of the Picklist values after creating
> > > this Rule, nor did I change the Display Name, Schema Name, or Lable Name.
> > >
> > > So what gives??
> > >
> > >
> > > --MD
> > >