A new version of Bulk Edit has been published just in time for the holidays, check your site settings for the upgrade link now to install it.
Plus some bug fixes.
Happy holidays!
A new version of Bulk Edit should be available to update any time now via the SharePoint store (check your Site Contents list for the update if you’ve already installed).
Over the next week a completely new Bulk Edit package will roll out to the SharePoint Store, this will replace the old packaging requiring those with any previous version installed will (one day) have to re-install in order to get any future updates after v1.0.2. The reason for this is account related and unfortunately cannot be avoided so apologies in advance.
The updated Bulk Edit has been submitted to the app store and existing users may now see two versions of Bulk Edit in the store, although the old version of Bulk Edit will keep working as is for the future, in order to get future updates please check that you are using a version higher than v1.0.2.2.
Note: No change other than the publisher profile will happen for Bulk Edit, it will remain free and feature complete now and forever. This change is only required to consolidate Nearbaseline’s App store profiles so I apologize for this inconvenience.
Just approved on the SharePoint App store is an update to Bulk Edit, if you’ve already installed then in the next 24 hours it should notify you of the update from Site Contents in PWA.
Go to the Bulk Edit page for Download and Support links.
Please leave any feedback here or support questions in the Support Forum.
Also if you use / like this app then please review and rate it it on the Microsoft App store!
I’ve been busy the last couple of months working away at my first crack at a SharePoint App as some of my recent posts here probably show. (Next up; a desperately needed refresh for this site!) So for anyone thinking about doing the same I thought it worth sharing some of my experiences in a quick write up.
However firstly: Go download Bulk Edit from the SharePoint App store right now! (And write a review!)
The first thing to say is when compared to the PSI API of the past even despite the near complete lack of documentation on JSOM / CSOM I’m loving it! To be able to write code that actually doesn’t fail half the time, who would of thought it possible?! :)
It’s early days yet, but what I can comment on so far is actually getting on to the Market place which in the end was in fact easier than I expected.
It took a couple of days to get my Seller account approved which was actually the longest wait. After that my app was approved within 48 hours of the second submission, that’s after the first submission was rejected within a few hours due to one of the automated-checks (make sure to read the links below).
To be honest the hardest thing was getting the App submission page to accept my Office365 subscription as “paid”, basically it requires a fully paid subscription linked to your seller account before you can submit a SharePoint app. The catch is that Partner accounts and trial accounts among others are not automatically accepted.
I’m now the proud owner of three O386 subscriptions; TechNet, MSPartner, and PAID MSDN Developer, yep I got there eventually!
If you have problems linking you account (steps here) make sure you give it some time, in my case it took overnight before the ‘verified’ subscription was accepted after following the verification steps.
Read the following if you want to know more on this process:
I’ve spoken to many people and read many other peoples thoughts on the whole new app model, seems to be a topic that divides opinions quite nicely.
I have to say in summary I do see some serious potential in the new model, sure SharePoint hosted apps are very constrained and Provider / Auto hosted are going to be an administrative nightmare in any typical highly locked down enterprise environment. But even still separating the solutions from SharePoint is a game changer in my opinion, that would be me coming squarely from the OPS site of DevOps!. That combined with solid client side APIs makes me actually happy to change from the old ways and old APIs.