How is everyone’s experience with Kinetic BAQ designer? As i try to embrace and adopt Kinetic, gee whiz. It seriously needs a quality evaluation or something. Some of the issues are so sporadic, I cant replicate on demand to send to tech support.
Here are some of the issue I’ve run into:
Calculated fields don’t save after hitting apply.
Adding parameters in calculated fields is spotty, sometimes i have to add the prefix “@”, sometimes I don’t need it.
In table criteria, the field name drop down menu comes up blank, i would have to refresh a few times or just click around, eventually it will populate.
Table relations would display a join for completely 2 different tables in the query.
again, its sporadic, and wanted to share and receive some feedback for the community
I was just working on a BAQ in the new designer and ran into an issue with SubQuery Name lengths.
The length of the subquery cannot be more then 20 characters. When I created the subquery, there was no issue.
I went about creating the BAQ and the various joins between the subqueries and tried to save the error was “Name greater than 20 characters”
After looking around - I finally figured out that the error was due to the SubQueries.
You can’t change the name because they had been used, but I didn’t want to delete them without rebuilding.
I used the new capability of copying the subquery and giving is a new shorter name.
Then after remapping a few things, deleted the subqueries, I was able to save the BAQ.
The calculated field editor needs to change the tree navigation so you can actually read what the field names and expand the list to find the fields. Same with the function list.
Still finding that I have to go back to Classic to handle Updatable and Advanced Grouping in those editors.
The BAQ editor is one of the last things that they did, and needs the most work to make it work. It’s come a long way, but it does still have some work to get to parity. Just know that and go with with an attitude that some things might not work and you have to fall back to classic.
Yes, but even with the bugs its still better than classic. Copying subqueries? Type to find instead of endless scrolling? Reference queries? Running subqueries individually? I will put up with the bugs for the massive functionality enhancements.
I still prefer Classic at this point because of the bugs. I do alot of importing and exporting of standard BAQ’s, especially during an implementation. At least on the desktop app, once I import a query, I have to close the screen and open back up to import the next one.
Submit bug reports to EpiCare, and it’ll get fixed. Even if you can’t replicate on-demand, it needs to get on their radar. Do a screen recording so they see something going wrong (I use ScreenToGif, collegues sometimes record a solo Teams meeting to get audio).
The sooner Epicor’s devs look at it, the earlier we get them fixed. Hopefully for 2024.2!
Since we’re beta testers on new Kinetic apps, we should get a bounty for each bug report accepted - how about $25 credit towards maintenance, lol!
In windows 11 you can now do a screen recording with the snipping tool which is also pretty convenient. However I find that submitting a screen recording to support only prompts them to ask for a meeting to demonstrate literally the same thing that is already in the recording.
Better than just a screen recording, consider other tracing options like @jgiese.wci’s and @josecgomez’s Kinetic Trace Utility or a screen capture utility that also creates a .har file which contains each and every REST call and response. I would think that is all support would need.
