If Visual Studio is closed, IIS is running, D365 will run based of your AOSService site.

If Visual Studio is closed, your IIS is stopped, D365 url will give you a Service Unavailable error.

If Visual Studio is open, your IIS is stopped, D365 would still run on based on IIS Express.

I ran a few scenarios after this so here is a list of them.

After some research I got to know that after the recent platform update 12 D365 is hosted on IIS Express, and as you know IIS express runs on visual studio, so if you have Visual studio open your app will be hosted. I’m sure this would not be a mystery for everyone but for a short time it became a mystery to me and might become to some others as well so I had to get to the bottom of the magic happening. I verified the app is connecting to the right database and verified the webconfig file points to my own server so some other machine could not be hosting the App, I checked all configurations and none point to a different server so what magic is going on here. How could this be? Its a single box Azure VM and everything, not just the AOSService but ISS itself is off. Mystery: IIS was stopped but D365 app was still running. Will discuss this further in my next blog.įor more information about date effectivity in data entities see: Date effectivity Keeps track of latest and old records rather than overriding existing records on update. What this means is that our data entity has at least one date effective data source and itself implements the date effective framework. Parent data source DirPartyTable, not DateEffective:Ĭhild data source DirPersonName, that is date effective: To configure it we simply need to set the Apply Date Filter Property to Yes for DirPersonName and make sure we add the ValidTo and ValidFrom fields of DirPersonName datasource to the entity field list. In order to make sure that we get the latest names of this party while exporting data we need to configure the entity to do so, else it will send whatever record is first in DirPersonName against the party record. Now the Party record is saved under DirPartyTable that is not date effective but its First, Middle and Last names are stored in DirPersonName table that is date effective. Data entity is not date effective but one or more data sources within the entity are date effective.įor example we have to export details of a Party record. When creating a data entity for a data effective table there are a few properties we need to consider for our imports and exports to work correctly.

D365 stop aos web service