Forum Replies Created
-
AuthorPosts
-
Martin LaukkanenKeymaster
Hello,
It sounds like the projects are being left checked out by the update, this could happen in the case of an error updating a specific field. Does it affect all project edits? Also do you receive an error message?
Either way the fix is simple; open Server Settings -> Force Check-in projects.
Regards,
Martin LaukkanenKeymasterHi,
Bulk Edit requires a Microsoft Project Server 2013, 2016 or Project Online deployment to install on. If you have this already then make sure you are trying to Add the app under a site collection with Project Server ‘PWA’ features activated.
Thanks,
Martin LaukkanenKeymasterHi,
Please try and clear the cache in your browser or try from another browser / machine. This can happen when the SharePoint ribbon menu is cached by your browser and the url to the newly deployed app was not updated yet.
Otherwise if this is your first app install, please check your server farm configurations, perhaps by ensuring that other apps work, if not then there may be a configuration issue with DNS in your SharePoint App Management service.
Hope that helps,
MartinMartin LaukkanenKeymasterHello,
As the upgrade is controlled by the SharePoint farm the best I can suggest is to uninstall / resinstall if you see this issue repeatedly.
Otherwise if it is an on-premises installation then you can review the ULS log for more information.
Regards,
Martin
Martin LaukkanenKeymasterHello,
Yes Bulk Edit can update project names as well as custom fields in Project Online (& on prem).
Cheers,
December 5, 2016 at 8:58 pm in reply to: Bulk Edit App Error loading page, error was: error details: Unauthorized #100957Martin LaukkanenKeymasterHello,
Based on the issue detailed, in particular that other apps also fail with similar errors, my guess is that PWA does not have access to the App Management Service itself. So in other words rather than it being a permission problem in the PWA configuration, actually the permissions configured in the SharePoint farm for Project Server and apps are not correct.
Check the permissions granted to the Project Server service account configured in CA and compare it between DEV and UAT, specifically what permissions are granted to the App Management Service and database(s) configured.
From memory the Project Server service account will need explicit access to the app management service.
Hope that helps you find the cause of this issue.
Regards,
MartinMartin LaukkanenKeymasterHi Rudi,
As I understand when configured for admin approval, the app will not be auto-installed. Once approved you will still need to open Site Contents and Add an App, there you should now be able to see the Bulk Edit app in the list of apps and be able to choose install.Is that possible?
Regards,
Martin LaukkanenKeymasterHello,
It sounds as if the app is simply not added/enabled on the PWA Site Collection, can you open Site Contents in PWA and if you do not see the Bulk Edit app listed there, then click Add new Add-in. Do you see it in the list of available add-in’s? Also can you add it? Or does it indicate that the app cannot be installed here, or similar?
Thanks
MartinMartin LaukkanenKeymasterHello,
I don’t provide direct downloads of the app files, as it is not possible to then control their distribution etc, however please use the contact form on this site and I can provide you with a limited licensed copy (to your company / name) to download directly.
Regards,
MartinSeptember 29, 2016 at 5:54 pm in reply to: Sorry the update failed, ensure that the project is not checked out #100756Martin LaukkanenKeymasterHi,
This is a known issue with non-English PWA instances at the moment, I have just this week (27/09) submitted a bug fix to Microsoft to be approved for release so please check back in a few working days for an update.
Regards,
Martin
Martin LaukkanenKeymasterHello,
For 2010 the Bulk Edit Tool from MSDN is available here: https://gallery.technet.microsoft.com/projectserver/Server-2010-Bulk-Edit-Tool-688f4dea
Otherwise for 2013 and 2016 this Bulk Edit too is available.
Regards,
Martin LaukkanenKeymasterHi,
Can you both check the following to resolve this:
- Permissions: The user running Bulk Edit must have OData access, so they need to be in the Portfolio Managers Group as a minimum, see the section “Security Requirements” here https://nearbaseline.com/apps/bulkedit/support/ if you need more info on this.
- Language: From my testing I can see that if the user’s default language is not English and the PWA site collection is configured to support multiple languages (Site Settings -> Language Settings -> Additional Languages) then this issue can occur on the latest version of Project Server (/ Project Online). Please test this by changing your user profile from ‘About Me -> Edit Profile -> Language and Region’ in Project Server, or ‘My Settings -> My Lanague’ in Project Online.
If the problem is due to language then keep an eye out for the latest version of Bulk Edit with a fix to this issue.
Regards,
- This reply was modified 8 years, 3 months ago by Martin Laukkanen.
March 11, 2016 at 6:09 pm in reply to: Bulk Edit Tool – can we install in an on premise environment #99481Martin LaukkanenKeymasterYes.
Please see https://nearbaseline.com/apps/bulkedit/support/ for some common issues faced with on-premises installations, however this app was designed and built on-premises and definitely supports the configuration.
However you will need to have your SharePoint administrators deploy the App Management service which is required by all Project / SharePoint 2013 apps.
Martin LaukkanenKeymasterHello,
Unfortunately not, the only option I can suggest is once you have opened Bulk Edit then you can use the column filters to filter by a specific field in order to filter out the projects you do not want.
March 11, 2016 at 6:05 pm in reply to: App is visible on Project Centre ribbon menu under Apps. #99462Martin LaukkanenKeymasterHi, Please see the FAQ under: https://nearbaseline.com/apps/bulkedit/support/
This issue is usually caused by the browser cache which does not update quickly enough in this case. Clearing the cache or testing from another browser / computer should resolve the issue.
-
AuthorPosts