Settings and activity
79 results found
-
6 votes
Bob Gaydos
shared this idea
·
-
2 votes
Bob Gaydos
supported this idea
·
-
6 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Bob Gaydos
supported this idea
·
-
35 votes
An error occurred while saving the comment
Bob Gaydos
supported this idea
·
-
7 votes
Bob Gaydos
shared this idea
·
-
32 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
22 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
42 votes
Bob Gaydos
supported this idea
·
-
40 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
46 votes
This enhancement is planned for Sierra 6.6.
Bob Gaydos
supported this idea
·
-
45 votes
Bob Gaydos
supported this idea
·
-
42 votes
The product manager will review this idea for possible inclusion in a future release.
Bob Gaydos
supported this idea
·
-
25 votes
This enhancement is planned for Sierra 6.6.
Bob Gaydos
supported this idea
·
An error occurred while saving the comment
Bob Gaydos
commented
Please consider implementing this functionality in the manner I proposed in the idea https://ideas.iii.com/forums/951745-ils-sierra/suggestions/50262807-rearchitect-iiirecord-record-metadata-to-provide-i
-
14 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Bob Gaydos
supported this idea
·
-
18 votes
Bob Gaydos
supported this idea
·
-
29 votes
Bob 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
·
-
54 votes
Bob Gaydos
supported this idea
·
-
6 votes
Bob Gaydos
supported this idea
·
-
4 votes
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.