‘QueryResultDataSetUbaqTableset’ does not contain a definition for ‘WriteXml’ and no accessible extension method ‘WriteXml’ accepting a first argument of type ‘QueryResultDataSetUbaqTableset’ could be found (are you missing a using directive or an assembly reference?)
I have System.Data and System.Data.Extensions in my References and System.Data as a Using
So it is not dataset, it is tableset with dataset name. then you cannot use this method.
I don’t remember if any dump method for tableset exist, so you have to use usual foreach to go through table rows.
This is the way. Very, very, very rarely should you fire off an alert immediately. Better to batch items and send them out periodically. Cuts down on inbox clutter and therefore reduces the changes of something getting missed. Users usually like it better too.
So it turns out the email is not being sent because the condition fails…more on that below, first…
I’m not saying the “less spam” idea is bad, it may work for some companies better than others and depend on the circumstance (timing, frequency, urgency), the main point is Method Directives are supposed to work the same in Classic as Kinetic/Web-UI and this is a general problem with Conditions, (not sending emails)
Okay, back to the situation, here is my oh so simple method directive:
The conditions logic is this:
It seems to me that the issue is there is no queryResultDataset in Kinetic Web-UI,
However, if you look at the trace in Kinetic it does show a view (Ctrl-Alt-View in Debug mode) called OFBPreflight_0_0 and OFBPreflight_0_1
this sounds wrong. I don’t think it is true.
You probably need to report it with very simple UBAQ/BPM attached for the investigation.
Meanwhile you can use some other condition, like check DB instead of checking incoming tableset.
My main suspicion is that in classic, there are 2 records set from the client - before changes and changed. And maybe the condition you use relies on this information.
In REST it is not required and overall should not be used, because server should not rely on info sent by client. But maybe in your case it is essential for condition to work.