Settings and activity
98 results found
-
14 votes
Bob Gaydos
supported this idea
·
-
26 votes
Bob Gaydos
supported this idea
·
-
9 votes
Bob Gaydos
shared this idea
·
-
2 votes
Bob Gaydos
supported this idea
·
-
44 votes
An error occurred while saving the comment
Bob Gaydos
supported this idea
·
-
11 votes
Bob Gaydos
shared this idea
·
-
42 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
48 votes
Bob Gaydos
supported this idea
·
-
50 votes
The product team will review this idea for consideration for a future release.
Bob Gaydos
supported this idea
·
-
19 votes
Planned for the Sierra May 2027 release (v7.1)
Bob Gaydos
supported this idea
·
-
39 votes
Bob Gaydos
supported this idea
·
-
13 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
·
-
80 votes
Planned for the Sierra May 2027 release (v7.1)
Bob Gaydos
supported this idea
·
-
6 votes
Bob Gaydos
supported this idea
·
-
4 votes
Bob Gaydos
supported this idea
·
-
5 votes
Bob Gaydos
supported this idea
·
-
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 votes
Bob Gaydos
shared this idea
·
-
5 votes
Bob Gaydos
shared this idea
·
-
12 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.