Hi @nickcerriIV 

There is no action call is defined in the import scenario ?

Thanks

@manikantad18 - it’s the last line

@manikantad18 the scenario you proposed results in error.  I’ve copied the trace below
 

Hi @nickcerriIV 

Try this one:

Thanks, @kbeatty21 - I’m having a real difficult time trying to open that file, though.  Screenshot?

Hi @nickcerriIV 

hmm - thanks again, @kbeatty21 .  I removed all but the quote number and the <Action: Convert to Project> line Unfortunately, I’m still running into an error.  The trace seems to always be “LINQ fallback!  Consider rewriting your query.”

Do you have any restrictions on the import?

@kbeatty21 Indeed I do.  The source restrictions limit the selection to only Prepared quotes.  Logic here is that the business event should only convert projects that have been approved (approval > prepared > convert)

@kbeatty21 Indeed I do.  The source restrictions limit the selection to only Prepared quotes.  Logic here is that the business event should only convert projects that have been approved (approval > prepared > convert)

 

It may have something to do with the value. 

@kbeatty21 Tried out a few variations (=’A’, ‘A’, etc.) and the only way I can get the scenario to pull in any data is to have it simply read A (or whatever dropdown value is required).  I verified that the screen was correct by changing the scenario to perform a submit action instead - this worked just fine.  I also played around with target restrictions instead of source restrictions.  Again, no luck.  

Hi there, I am having this exact issue.  Were you ever able to get it to work?

@matthewhill - I know it’s been a bit, but you won’t be able to perform this as an import scenario because it touches more than one screen.  This would probably need to be handled as a customization.  Depending on how many quotes you process daily, it would be very useful to have a processing screen that handles this.