PSA & Field Service Schedule Board Error

Recently I ran into this little issue when trying to access the D365 schedule board for both PSA and Field Service. “Resource not found for segment ‘msdyn_FpsAction’. There were also a bunch of other general SQL / Unexpected errors when I was trying to access projects within PSA. This happened immediately after I installed the Microsoft Partner Portal solution with the additional PSA extension.

Basically, every blog I went to pointed me to the same link, which didn’t seem to work :(

So, for those of you that run into this error in the future, It has to do with certain processes being in Draft mode. I also discovered that a load of these processes didn’t even have an owner.

Firstly, I assigned the processes to myself.

Then activate the processes that had randomly been deactivated for no reason. This will then show the schedule board.

Viola… Your schedule board should now work…AND you shouldn’t get any random errors when trying to save projects. Seems the Partner Portal installation with the additional PSA extension deactivated a load of Actions and workflows and didn't reactivate them. 

Dynamics 365 User Group – Birmingham – 17 May 2018

Recently I had the pleasure of presenting at the D365 Birmingham User Group Meeting. Thanks to everyone that attended. Was really fun and I learnt a whole lot. For those of you that haven’t been to one of the D365UG meetings, and if you are utilising Dynamics 365, I suggest that you join and get involved.

I had the pleasure of following Julian Sharp, an absolute legend in the D365 world and a brilliant trainer whose focus is “Helping organisations make the most of Dynamics 365 Customer Engagement through advice, optimisation and training”.

 Julian gave a great presentation on the importance of Dynamics 365 Customer Engagement exams and as well as how to prepare for them and how to study. You can follow Julian on twitter using this handle: @Julianatvigence or check out his blog here for some really useful information.

My presentation was focused on why brand perception is so important within a business and the ability to generate more meaningful conversations with your customers utilising Dynamics 365 Customer Engagement. This presentation was a “Spin Off” of the one I did at the D365 User Group Summit event. I only used Microsoft Social Engagement as the channel of interaction rather than use a load of channels. More information regarding this session can be found in my next post (Awaiting Hyperlink).

Just a quick summary of what the User Group is all about… it’s not a sales pitch for Dynamics, but more of a community lead initiative that enables the community to help and assist one another regarding all things Dynamics 365 related. There is a big mix of Dynamics 365 customers, Partners, ISVs and even Microsoft guests.

I’ve found it massively useful because the people part of the community just want to help and share info. It’s a super relaxed environment that promotes learning and development. To find out more and to even register, follow this link and get stuck in. There are User Group chapters popping up all over the place. Hope to see you there.

Follow the Dynamics 365 UK user Group on Twitter using the following handle: @CRMUGUK 

"UNEXPECTED ERROR" on Record Creation / Update in a Workflow

I’m going to share something life changing with you right now. Perhaps I’m the only one that ever experienced this… who knows, but I thought I’d share it anyway.

Have you ever created a workflow and added the “Update / Create Record” function? Have you ever created an “Automated Record Creation Rule” and added the same function? Have you ever received the below error? I’ve found that this generally happens on the Case entity…

WELL… If you have ever encountered this delightful little issue, then you are in the right place. After beating my head against a wall, I discovered that this appears when you activate and publish the Knowledge base functionality to the associated entity… This is why it was happening on the case record.

To resolve, simple pop into the relevant entity and disable the KB functionality on the forms.

The thing that made me very sad was that I discovered I needed to disable this on all the forms, not only the primary form. This may be an issue if you have a load of different forms.

Once I had disabled the KB functionality I could set the update fields in the case entity.

Once all your updates are made, simply go back into the case entity and re-enable the KB functionality J

I hope this helps someone because I fought for a while to get this right and I couldn’t find a load of stuff on the web.