Steve Bromschwig
My feedback
28 results found
-
8 votes
An error occurred while saving the comment Steve Bromschwig
supported this idea
·
-
7 votesUnder review · 1 comment · Feature Suggestions for Maximizer CRM » Usability - User Experience · Admin →Steve Bromschwig
shared this idea
·
-
154 votes
You can create a custom field (UDF) and then set it to True or False. Then using Advanced Search you can filter whether to show entries based on this custom field (UDF).
An error occurred while saving the comment Steve Bromschwig
commented
The downside is that this request was to implement a feature which would allow a user to "declutter" the Contact tab. If a Contact is no longer at the Company record, we typically do not want to delete the Contact from the database because doing so would impact historical data. So, the request was to allow these inactive Contacts to be hidden so they do not clutter up the list. There are many instance where a single Company can have hundreds of Contacts which have been entered in over the years. Over time, the sheer number of Contacts becomes overwhelming.
While a UDF could be used to track the Active / Inactive status of any given Contact, it doesn't do anything to "declutter" the grid as was the original request. Yes, you can include that UDF in the Column Setup and yes you can sort your Contact tab based on that UDF - but then that still leaves your list with potentially lots of irrelevant people which are preserved for historical purposes only.
Besides, I might want to sort my Contact tab based on some other field (Title, Department, Email, some other custom UDF), so adding *another* UDF to the equation is not the preferred approach.
Steve Bromschwig
shared this idea
·
-
97 votes
An error occurred while saving the comment Steve Bromschwig
commented
John,
Your solution of simply adding "IBM (International Business Machines)" as the Company Name is definitely a work-around to the limitation of having only a single Company field - and it's one that I've used with clients previously.
In most cases, it works fine - but looks really tacky (for lack of a better word) when you generate mailing labels from your Maximizer list - or if you are generating a report that needs to be transmitted to the Company.
Ian - I like your feedback on the "include nicknames" checkbox being a self-remembering setting and/or a user preference.
I hadn't thought about making the Alias/Nickname field available as something that could be placed in a Column Setup, but I think that makes sense. Again, treat is as an entity separate from the formal Company field - but I could see value in allowing it be be placed in a Column Setup.
An error occurred while saving the comment Steve Bromschwig
commented
I would like to see this separated into multiple fields. If I am generating a mailing label, or printing a formal report, I would want the name of the company to display as "International Business Machines", not "International Business Machines (IBM)".
Steve Bromschwig
shared this idea
·
-
3 votes
An error occurred while saving the comment Steve Bromschwig
commented
Paul, I agree with Connie - this sounds exactly like what a Catalog Search will give to you. Favorite Lists are snapshots of the Address Book list at a specific point in time. Catalog Searches will always re-query the database to bring back the most current list of records matching the specified criteria.
-
143 votes
Please note Maximizer’s professional service team have created integrations with Avaya AES among others so feel free to contact them directly if you have an acute need for this type of integration.
Steve Bromschwig
supported this idea
·
-
26 votesSteve Bromschwig
supported this idea
·
An error occurred while saving the comment Steve Bromschwig
commented
This would be a very welcome feature when having to administer more than a handful of users. It would simplify the administration process and reduce the amount of time required to perform straightforward tasks.
-
52 votesSteve Bromschwig
shared this idea
·
Yes, this would be a simple and effective change.
As a workaround, I simply rename these groups something like:
SYS [Legacy] - Crystal Reports Users
SYS [Legacy] - SSRS Report Management
This effectively bubbles these groups to the bottom of the list and I ensure no users are actually added to them. This, coupled with the "show only groups user is a member of setting" generally removes them from the UI and avoids incorrect usage.