02-07-2020 09:51 AM
Is anyone else having problems with NI Support abandoning tickets instead of working on them?
Or is it just me?
02-07-2020 10:04 AM
What are the ticket numbers?
Of course it happens but it shouldn't be typical.
02-07-2020 10:21 AM
@Jacobson-ni wrote:
What are the ticket numbers?
Of course it happens but it shouldn't be typical.
#7794213
02-13-2020 06:35 AM
@Jacobson-ni wrote:
What are the ticket numbers?
Of course it happens but it shouldn't be typical.
Right, it shouldn't be typical. But unfortunately, it is.
02-13-2020 02:44 PM
Here is how the current NI support model looks from my perspective:
I've just passed step 4 again (now on my 6th support engineer). Maybe 6th time is the charm.
02-13-2020 02:58 PM - edited 02-13-2020 02:58 PM
Hi Paul, it may be related to complexity of the ticket. If it has to do with some of your XNode code (for example), there might not be as many people that can help. Or they might have to choose between closing 10 easy tickets or 1 paul_cardinale ticket. I'm not trying to make excuses for NI, just offering an explanation why your ticket gets lost while others might not. I do hope the 6th time's the charm.
02-13-2020 03:14 PM
It turns out that the 6th time was the charm.
Support engineer Adam Hennad solved the problem (and rather quickly).
02-13-2020 04:06 PM - edited 02-13-2020 04:06 PM
@Gregory wrote:
Or they might have to choose between closing 10 easy tickets or 1 paul_cardinale ticket.
Yes this is becoming very common everywhere as service personal are basically internally rated and reviewed on the number of service requests CLOSED. (Complexity of the issue is not a factor on the spreadsheet some manager sees showing how many service requests you received and how many you closed in a timely manner)
So if your issue can't be solved in a day or two, you are going to get put on back burner because they have to close some easy tickets to keep their numbers up.
02-13-2020 08:34 PM - edited 02-13-2020 08:35 PM
I've seen an SE signature stating if I don't respond to their email within 3 days, the request will marked as resolved and automatically closed. Never mind if I'm busy, or unavailable for some reason.
"If there is no reply within 3 days, the service is determined to be resolved and the SR is automatically closed. If you have more questions after denoted period, you will need to request technical support again."
This was after more than a week of my submitting an SR and hearing nothing out of support 🤔
That is, if I can submit a request in the first place...
Any sort of KPI or performance indicator based on tickets closed is stupid. If there are performance metrics measured, there are performance metrics to be gamed.
02-14-2020 06:21 AM
@Gregory wrote:
Hi Paul, it may be related to complexity of the ticket. If it has to do with some of your XNode code (for example), there might not be as many people that can help. Or they might have to choose between closing 10 easy tickets or 1 paul_cardinale ticket. I'm not trying to make excuses for NI, just offering an explanation why your ticket gets lost while others might not. I do hope the 6th time's the charm.
It had nothing to do with XNodes (I wouldn't even bother asking for support on XNodes); it was an app builder issue.
It turns out that if you're using LV2018 and running a Source Distribution buildspec, and VIs in your project call malleable VIs that are in your project and those malleable VIs call sub VIs that are also in your project and your buildspec has "Remove unused polymorphic VI instances" checked, then when the buildspec runs, the malleable VIs will get converted into Express VIs, and the subVI calls inside the (former) malleable VIs will be wrongly linked: They will be linked to the original versions in the project source instead of the copies in the source distribution build. This results in a broken source distribution. The solution was just to uncheck "Remove unused polymorphic VI instances" in the buildspec (I had tried many many things to try to solve the problem, but that never occurred to me).