François Renaville
My feedback
42 results found
-
465 votes
This improvement is planned for the 2024 Roadmap.
-
38 votes
-
49 votes
This is planned to be developed as part of NERS #8134 for a closed list of labels provided by the community.
An error occurred while saving the comment -
192 votes
-
16 votes
-
60 votes
An error occurred while saving the comment I forgot to update this idea, sorry. We noticed last summer that behavior had changed and that app users could go back to Primo PI search results in all circumstances. So, the known issue must have been fixed, although I must have missed the information. Thanks to all who supported the idea. ;-)
-
13 votes
-
19 votes
-
509 votes
We are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.
An error occurred while saving the comment I agree that it is always painful when Discovery Import Profiles (Import Data to Primo VE) complete with errors because some harvested records failed to load. We must always open a case and provide the process ID, so that Support can tell us which records could not be imported. Of course, we rarely get an answer in the next fex days at Tier 1... If we could directly see in the job Report which records have failed, we could quickly fix the issue ourselves, either in correctling the source data (if they are ours) or by updating our normalization rules accordingly.
-
105 votes
-
71 votes
-
88 votes
-
316 votes
-
36 votes
Hi,
We would like to update that this idea is still not planned, but still being examined for a future release.
Best regards,
Yael.
-
87 votes
-
140 votes
-
69 votes
-
42 votes
-
313 votes
-
148 votes
+1