Displaying SharePoint Documents in a D365 CE Form

Andrew Robilliard — Tue, 17 Nov 2020 03:52:45 +0000

Displaying SharePoint documents for an entity in Dynamics 365 CRM/CE has been a common requirement for a long time. For many years, the go-to fix was using an embedded IFrame on the form, pointed at the document relationship. However, this was always unsupported and was sure to break at some point...

It turns out it finally did. If you follow along with the original approach, seen here on Jason Lattimer's blog, you'll find that the 'Upload' functionality now breaks if your organization has transitioned to the Unified Interface.

The New Approach

It turns out, Microsoft has finally introduced a way to add this functionality out of the box. However, unless I've missed something, they haven't really talked about it anywhere. Hopefully, that's where this blog post comes in.

Steps

Before starting, it is important to note that this only works on D365 CE online instances that have transitioned to the Unified Interface.

I also assume that you have already set up Sharepoint Document management for the entity in question.

Navigate to https://make.powerapps.com, and open the entity form that you want to add documents to.
Add a subgrid of 'related records' only, pointing at entity type 'Documents (Regarding)'

Important note: this subgrid can only be added using the new form editor. The 'Documents' entity will not be available in the legacy version.

After adding the subgrid, save and publish your form, and open it in the Unified Interface.

You should now see a new Documents sub-grid, with the same contents as under the --> Regarding --> Documents tab.

Happy documenting! ✍

Deploying .NET Core to Heroku

Andrew Robilliard — Mon, 31 Aug 2020 05:04:55 +0000

I've always loved coding in C#. Equally, I love using Heroku to host personal projects - they have a nice UI, and a free tier!

However, there are a few limitations. Notably, .NET Core is not supported out of the box 😢. We can fix that!

The Fix

While Heroku isn't able to run C# code directly, they do have support for Docker containers. With that our solution is clear - dockerize all the things!

Deploying a .NET Core App to Docker

The following is not meant to be a .NET Core course, but you might pick up some basics on navigating the base files if you're a beginner. What we will cover:

Creating a new .NET Core MVC project from the command-line
Modifying the base files to be Heroku & Docker compatible
Configuring a new Heroku app
Deploy our app to Heroku 🚀

1. Getting Started

Before we get into changing some code, we need to get our foundation components in order. Before continuing, you should have:

.NET Core installed on your device
- I'm using v3.1 for this tutorial, which can be found here
Docker installed on your device
- You can follow the steps here
A Heroku account! - https://signup.heroku.com/
Install the Heroku CLI, which allows us to communicate with the Container Registry.

With those out of the way, we're ready to go.

2. Creating a New .NET Core App

First off, we need to create our new .NET Core app. I'll be following the steps for setting up a basic .NET Core MVC project, which can be found here.

3. Setting Up a New Dockerfile

The dockerfile required is pretty basic, with nothing too complex happening.

# Dockerfile

FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
WORKDIR /app

# Copy csproj and restore as distinct layers
COPY *.csproj ./
RUN dotnet restore

# Copy everything else and build
COPY . .
RUN dotnet publish -c Release -o out

# Build runtime image
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1
WORKDIR /app
COPY --from=build-env /app/out .

# Run the app on container startup
# Use your project name for the second parameter
# e.g. MyProject.dll
ENTRYPOINT [ "dotnet", "HerokuApp.dll" ]

Additionally, you should probably setup a .dockerignore file to keep your image size down.

# .dockerignore

bin/
obj/

If you want to test out your container, you can run

docker build -t YourAppName .

# The name variable (abc) is simply used to refer to the 
# container later when we want to close everything down.
docker run -d -p 8080:80 --name abc YourAppName

Navigate to http://localhost:8080 and you should see your app running.

All looking okay? Great! Lets shutdown the container locally. We don't need it running here if it's about to be up on the internet!

docker rm --force abc

4. Configuring a New App in Heroku

Sign into Heroku, and create a new app from your personal dashboard at https://dashboard.heroku.com/apps
- You'll need to provide an app name, and deployment region
Heroku will then display the various deployment options. We're going to be using Container Registry

5. Releasing to Heroku 🚀

Last but not least, let's get it online.

1. Using the command-line, login to the Heroku container registry

heroku container:login

2. If you didn't above, make sure you build your docker
container!

docker build -t YourAppName .

3. Push your newly built container up to Heroku

# 'YourAppName' should be the name of the app you 
# configured in Heroku in step 4.
heroku container:push -a YourAppName web

4. Finally, release!

heroku container:release -a YourAppName web

Now, if you just navigate to https://your-app-name.herokuapp.com, you should see the base app. Wait... that didn't work! What happend?!

Take a look at the heroku logs

heroku logs --tail

Within the scary looking logs, you'll see that .NET Core failed to start 'Kestrel', which is the web server for .NET Core. This means our app wasn't able to launch 😢.

If you remember when we started our docker container locally back when we configure it, one of the parameters we passed was a port. When Heroku gives us a port to use, our app needs to know about it!

Modify the end of the Dockerfile to be

# Dockerfile

# ...

# ENTRYPOINT [ "dotnet", "HerokuApp.dll" ]
# Use the following instead for Heroku
CMD ASPNETCORE_URLS=http://*:$PORT dotnet HerokuApp.dll

This allows the our container to use the Heroku-provided port on startup.

Re-deploy everything to Heroku:

Build docker image
Do a heroku container:push
Do a heroku container:release

And voila - your very own .NET Core app hosted on the web.

Conclusion

I hope the above tutorial is helpful, and allows some newbies to get started on their own .NET Core side projects.

If anyone reading has some extra tips, or a better approach, please leave a comment below!

Thanks for reading 👋

DEV Community: Andrew Robilliard