Hans Meyers
My feedback
2 results found
-
0 votes
An error occurred while saving the comment An error occurred while saving the comment Hans Meyers
commented
Oops, I was a little premature. When clicking on the displayed Asset Library in OnePlaceMail, we get an error message (see screenshot). The error isn't blocking, because the image can be uploaded by closing the window with the error message, but it is annoying for the end-user.
https://d37wxxhohlp07s.cloudfront.net/s3_images/869881/erroropm.jpg?1362994284
An error occurred while saving the comment Hans Meyers
commented
Thanks Cameron for the support. It worked as described.
Hans Meyers
shared this idea
·
-
0 votes
An error occurred while saving the comment Hans Meyers
commented
Hi Ilia,
First of all, thanks for your time and help. I'd like to post that the sandbox solution works as you described! That is the good news :-)
We do have a couple of concerns:
1) When using the sandbox soluion in a site collection that has been created in another language than English (our company language is Dutch), the OnePlaceMail Email library cannot be seen in the library list.
2) We have a clear preference for a farm solution as opposed to a sandbox solution for the following reasons:
-- Using the sandbox solution, we need to deploy and activate the feature every time we provision a new site collection. This is tedious compared to the farm solution, where we can configure our site defintions to activate the required features at the moment the site collections are provisioned.
-- In the farm solution, 4 separate features are provided, while everything is grouped into one feature in the sandbox solution. This is not so convenient in those situations where we would want to activate specific features and not others.
Do you expect to offer the new features in the farm solution as well? Or will you only be working with the sandbox solution in future? We hope not, but if this were the case, perhaps it would be a good idea to remove the farm solution from your server component installations files so as not to confuse customers?
Thanks for your feedback!
An error occurred while saving the comment Hans Meyers
commented
Hello Ilia,
Thanks for your advice. In fact we are not using the OnePlaceMail SharePoint Sandbox Solution v3. Instead we are using the farm solution that is included in the package. Is there a specific reason we should be using the Sandbox solution rather than the farm solution? Is it best practise? How come the farm solution doesn't work?
We will test the Sandbox solution today and post our findings here.
An error occurred while saving the comment Hans Meyers
commented
Ilia, thanks for your insights.
If I understand Ilia's answer correctly, the "Email as Attachment" feature should work on any List Type, as long as it has associated with it the Content Type "Document" or any other Content Type derived from "Document". Is that correct?
We performed the following test:
1) Downloaded OnePlaceMail 6.3 from following link: http://www.scinaptic.com/support/0006.html
2) Installed the server component on a clean SharePoint 2010 test system and activated the feature on our site collection
3) Added a standard document library. The feature appears as expected :-)
4) Added a library of type Asset and associated the Content Type "Document" to it. Then added a document to this library, selecting the "Document" Content Type for it. The feature doesn't work :-(
When we looked at the feature.xml file in de server component that we installed, we can't seem to find anything that indicates the feature would work as you described.
Are we overlooking something? Thanks for any help!
Hans Meyers
shared this idea
·
Hi Cameron. Thanks for analysing this. Using SharePoint Manager, we were able to see the duplicate fields. However; when trying to reproduce the issue with new libraries, we were unable to create Asset Libraries with the duplicate field. Can you share with us in which cases you were able to create the duplicate fields? Is it safe to remove one of the duplicate fields?