Identifying Returns Affected by Changes

[kathyss]

My specific issue has to do with Proseries broken functionality of efiling KCMO RD-109. The efiling broke toward the end of the season without notice from Proseries (efiling looks like it's available but it doesn't efile). After 2 hours and 20 minutes with support it seems that Proseries was unaware of the problem and has little interest in fixing it.

I am suggesting that Proseries have a clear and easy way for users who have identified software errors to request that a new analyzer function be added to allow us to easily identify clients potentially affected by the error. If you give me an analyzer that will return a list of all returns containing RD-109 I can compare that list to the list of KC returns successfully efiled and have a relatively small list of remaining returns that may be affected rather than having to open up hundreds of returns to see where the problems are.

I am told that they will not do this for a customer -- how about doing it for all customers and all relevant errors and hiccups? Refusing to take the time to help me fix a client service problem that I have due to Intuit's error is, while fairly standard, an abdication of responsibility. 

Intuit boasts about the time savings they provide and I am grateful for software that is efficient. It's time to start tracking the amount of time spent on this issue and any others for which a supportive solutions or assistance is not provided.