By using this website, you agree to our Terms of Use (click here)
I'm adding this mainly for Acumatica partners who are running Acumatica internally.
The Cases in Acumatica work really well for technical support.
But one problem is that you wind up with a mountain of useful information without the ability to search it.
One way to get around this problem is to enable the universal search to "see" more stuff about a Case.
In my demo environment, I had the following case with the word "recommended" in the Case Details (also called the "body" of the case):
But when I did a universal search, I didn't get any results which made me sad.
Then I found this article by Doug Johnson which shows you how to add additional fields to universal search:
https://www.acumatica.com/blog/technical-tuesday-universal-search-in-acumatica/
I used the technique in that article to make it possible to search on the Case Details.
As you can see below, I am now able to search on "recommended" in the universal search and have it return my Case 000118:
How did I do this?
I just followed the instructions on the article from Doug Johnson to add the following little piece of code to a Customization Project:
Don't forget to run the Rebuild Full-Text Entity Index (SM209500) screen on the CRCase entity, something that is also mentioned in Doug's article:
Tim,
Once again, great article with specific instructions on how to get an immediate return with a very practical application as an example.
However, your article brings up a higher level question I as a non-developer have wrestled with; how do you bundle and document your customizations?
Regarding bundling, do you put each of these minor customizations into their own project to do you put several or all your minor tweaks into a single project? Each option has it's own drawbacks.
On documentation, how do you document your code, both internally andexternally, so you can find modifications you or others have made in a site?
Again, I am not a developer. I can do a very minor level of coding but only with extensive help from Google and and other reference sources.
As always, thanks in advance for your help and insight.
Hey Shawn,
As a non-developer myself, I'm not sure I'm much help here.
Personally though, I think multiple Customization Projects are better. It makes troubleshooting easier.
As far as documentation goes, my thoughts:
1. I don't think the developer is in a position to do this well. I think this is better done by the "business" person who can document what the customization does from a user's perspective.
2. A Microsoft Word document is good enough for me. Or, my personal favorite, a Google Doc so you can easily share the link. I like simple documents personally because they can easily be consumed by people. I prioritize mass consumption and spreading basic knowledge (80/20 rule) over fancy software tools that might do a "better" job of documentation, but are more difficult for EVERYONE to consume.
Online Members
