Settings and activity
87 results found
-
2 votes
Bob Gaydos
supported this idea
·
-
40 votes
An error occurred while saving the comment Bob Gaydos
supported this idea
·
-
9 votesBob Gaydos
shared this idea
·
-
38 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
26 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
Bob Gaydos
supported this idea
·
-
45 votesBob Gaydos
supported this idea
·
-
45 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
17 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Bob Gaydos
supported this idea
·
-
21 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
Bob Gaydos
supported this idea
·
-
36 votesBob Gaydos
supported this idea
·
-
11 votes
An error occurred while saving the comment Bob Gaydos
commented
In response to Jeremy's comment - thank you, Jeremy - my vision of writing to review files was more simplistic and does not require the dynamic flexibility of programmatically locating an open review file to use. Instead, I imagined using one or more existing review files dedicated to the purpose of the reports mentioned as the primary use case in my first paragraph above.
Granted, a robust record import mechanism external to the SDA or other related applications could absolutely benefit from adding the missing features Jeremy points out, so please add "capacity" (bool_info.max) to the /v6/reviewFiles GET request as well as a new parameter named something like "showUnusedFiles".
Bob Gaydos
shared this idea
·
-
68 votesBob Gaydos
supported this idea
·
-
6 votesBob Gaydos
supported this idea
·
-
4 votesBob Gaydos
supported this idea
·
-
5 votesBob Gaydos
supported this idea
·
-
29 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Bob Gaydos
commented
Since the goal is already doable, why don't we rephrase this idea as "Make it EASIER to search..."? The solution could then be to extend the "not exists" operator to more fields in more record types.
This admittedly gets a little tricky for fixed-length fields and would have to be implemented more sparingly there. Not Exists already works on Item Due Date; I'd like to see it work on fixed fields which are not assigned a default value, like Item Sticky Status.
-
14 votes
An error occurred while saving the comment Bob Gaydos
commented
I just realized that deletes of iii_user would result in null references from the many-to-many table described in step 1 above. Add a deletion_date_gmt column to iii_user (like record_metadata currently has) so that no iii_user rows are ever actually deleted.
Bob Gaydos
shared this idea
·
-
15 votesBob Gaydos
shared this idea
·
-
4 votesBob Gaydos
shared this idea
·
-
10 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
Thank you for writing up this enhancement request, Victor! No table as important as branches/location codes should be only partially exposed via the API. To paraphrase Queen. I want it all and I want it ...as soon as can reasonably be expected given our current position in the active development cycles.