Elliot Williams
My feedback
15 results found
-
40 votes
An error occurred while saving the comment Elliot Williams supported this idea · -
86 votesElliot Williams supported this idea ·
-
194 votesElliot Williams supported this idea ·
-
45 votesElliot Williams supported this idea ·
-
8 votesElliot Williams shared this idea ·
-
42 votesElliot Williams supported this idea ·
-
61 votes
An error occurred while saving the comment Elliot Williams commentedThis would also allow sites with standard sandboxes to test the feature more effectively. Since the standard sandbox doesn't have our local data, we can't see how the person entities would look for our actual records. Being able to enable it on specific views would allow us to see how it works with our real data, which would make it easier to make the case to colleagues for why this is a valuable feature.
Elliot Williams supported this idea · -
181 votesElliot Williams supported this idea ·
-
12 votesElliot Williams supported this idea ·
-
5 votesElliot Williams supported this idea ·
-
55 votesElliot Williams supported this idea ·
-
253 votesElliot Williams supported this idea ·
-
405 votesElliot Williams supported this idea ·
-
302 votesElliot Williams supported this idea ·
-
21 votes
An error occurred while saving the comment Elliot Williams commentedIt would be great to have this ability in Primo VE, as well. Right now, we have to individually create import profiles for each set we want to harvest, but in practice, the number of sets we don't want to harvest is much smaller than the number that we do want to harvest. It would be great if we could exclude the two sets we don't want, rather than having to create separate processes for the 18 sets we do want.
Elliot Williams supported this idea ·
This would be a big help for us, as well! We have one import profile that regularly fails, but occasionally others do, as well. It would make my life much easier if we could quickly and easily identify which job has failed.