8 results found
-
SmartFields - change default to Exclude (or allow us to choose our preferred default for our system)
Can there be a way to choose your system's preferred default for SmartField inclusion? Currently it defaults to Include. Ideally we'd much rather it default to Exclude, or at least give us the option to choose our default.
The issue is that with numerous system admins making changes or adding fields over time, we inevitably are forgetting to toggle this to Exclude and errant fields then show up in our exported pdf files - that we often are completely unaware of. This could cause a file to being shared with users who should not have access to some of the…
9 votes -
Permission Quick Edit: Security Matrix checkboxes for Fields
It would be really helpful to have the option in the various Security Matrix sections to toggle all the checkboxes on or off across for a particular field, not just down for a Role or Status.
And as we can do with the 3 dots in the header row to "Copy Row Settings", I'd like to be able to "Copy Field Settings".
Use Case: I have a similar update I'd like to make to a large number of new fields to remove all the current permissions and replace with updated permissions and need to go through each field and each…
6 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We will monitor interest for future consideration.
-
Record Lock Override Notification
When a user is being kicked out of a record, it would be great if they were notified that they were being kicked out.
9 votes -
Custom Fields Permission Quick Edit - freeze top/left headers for Role and Status; add in field Caption
When we need to update the custom field permissions, the Permission Quick Edit is often unusable. Once you scroll down a small amount, you lose the header row and can't tell what role or status you're changing. Same for when you scroll to the right, you lose the Custom Field column on the far left and have no idea what field you're editing.
We also usually don't really know the field's name as well as we know the Caption. It would be so helpful to include both the name and caption for reference so you know you're really updating the…
6 votes -
Give the option to just run a Charity Check report through the GuideStar extension, rather than it pulling the entire "Pro" report
A recent SmartSimple update included a change with the GuideStar Charity Check feature, where it now pulls a GuideStar Pro report versus just pulling the Charity Check report. I'm not sure if it's just us or if there are any other clients have found this to be burdensome to their processes for a couple of reasons.
1) It now takes so much longer for the report to be pulled into the record (at least 5-10 minutes). So, it's not as immediate as it once was.
2) We don't use all of the other information that is in the Pro report.…
4 votes -
Need to be able to attach an organization to L2 payment records
We need to be able to attach a payee organization on an L2 payment record that can be different from the org listed on the L1. We've had to create a number of inelegant workarounds in the record and in reporting to get payments to work for our business processes. If it worked like the standard organization field on the L1, that would be the functionality we need.
2 votesWould the Level 2 account association be sufficient to meet your needs?
-
Ability to Copy/Save As SmartVersions
We build funding applications using SmartVersions. Sometimes we have a minor update to a SmartVersion we would like to make for a future competition but want to keep the original SmartVersion as well. It would be great if we could Copy or Save As a SmartVersion the same way you can Copy or Save As a Custom Field so we don't have to start from scratch each time.
2 votes -
Dynamic Visibility should copy over to new System Versions
Currently, when SmartVersioning is used, it will copy over all the fields in the Core version to the new version. It does not, however, copy over the dynamic visibility. So if the dynamic visibility changes between versions, you have to manually keep all of your dynamic visibilities updated to the newest versions. This is a pain when you have to manage dozens of dynamic visibility fields.
It would make more sense that, if a dynamic visibility is set to the Core version, that it automatically adds the new version that is stamped from the Core. If fore some reason this…
1 vote
- Don't see your idea?