Quantcast
Channel: Microsoft Dynamics 365 Community
Viewing all 17314 articles
Browse latest View live

D365FO - Table Browser via web browser

$
0
0
In previous versions of AX you had a table browser in the AOT which allowed you to view the data, modify or delete it while executing any table methods that may have been associated with it. In D365 you can no longer access the table browser the same way as you not longer have access to the AOT in production. 

In non-production environment's and production environment you can use the following URL to open a web based table browser

You can access it via environment url/?mi=SysTableBrowser&tableName=[tablename]&cmp=[company]

Example: https://environment.cloudax.dynamics.com/?mi=SysTableBrowser&tableName=Hcmworker&cmp=MHC

Where HcmWorker is the table and the company is MHC



In non-production environments which you have access to visual studio you can also access the web table browser by right clicking on a table and choosing "Open table browser"




It is good to note that when using the visual studio method to open the table browser the company that is on your user account will be defaulted to

D365FO - Execute a job/runnable class outside of visual studio

$
0
0
In AX 2012 you had access to the AOT to run a job in non-prod and in production. However because you can no longer access the server itself nor visual studio which is now the AOT you may need to run a custom job created outside of visual studio. In order to do this we can run the following url

[D365FO main URL]/?cmp=[company]&mi=SysClassRunner&cls=[job/runnable class name]

OneBox Example:
https://usnconeboxax1aos.cloud.onebox.dynamics.com/?cmp=[company]&mi=SysClassRunner&cls=[job/runnable class name]
Example: https://usnconeboxax1aos.cloud.onebox.dynamics.com/?cmp=MyCompany&mi=SysClassRunner&cls=MyCustomJob

D365FO - Maintenance mode / Importing License File (ISV/VAR Add-on License import)

$
0
0
In AX 2012 in order to import a license file for an ISV or VAR add-on all you simply did was go to your license management form and click on import, select the file and run a full sync. In D365FO this has changed dramatically.


In D365FO there is now only a license configuration which is available via  System administration > Setup > License configuration however you will notice that the data is read-only.

(This form is read-only unless the system is in the maintenance mode. Maintenance mode can be enabled in this environment by running maintenance job from LCS, or using Deployment.Setup tool locally)

In order to change this from read-only to modifiable we need to put the system in maintenance mode. We do this by opening the command prompt (cmd.exe)

change the dir to your local \AosService\PackagesLocalDirectory\Bin\ folder:

>cd C:\AosService\PackagesLocalDirectory\Bin\

Put the service into maintenance mode:

>Microsoft.Dynamics.AX.Deployment.Setup.exe --metadatadir C:\AosService\PackagesLocalDirectory --bindir C:\AosService\PackagesLocalDirectory\Bin --sqlserver . --sqldatabase axdb --sqluser [sql login] --sqlpwd [sqlpassword] --setupmode maintenancemode --isinmaintenancemode true

Reset IIS/Cycle the AOS> IISRESET


The system should now be in maintenance mode so we can import the file

via the cmd.exe prompt run the following

Import license file:
> Microsoft.Dynamics.AX.Deployment.Setup.exe --setupmode importlicensefile --metadatadir C:\AOSService\PackagesLocalDirectory --bindir C:\AOSService\PackagesLocalDirectory --sqlserver . --sqldatabase AxDB --sqluser [sql login] --sqlpwd [sql password] --licensefilename C:\licensefolder\license2018.txt


In D365FO you should now be able to open  System administration > Setup > License configuration and not see the read-only warning. You should see the name of the license that was import and you should be able to enable the configuration for the new license file.





Turn off maintenance mode

> Microsoft.Dynamics.AX.Deployment.Setup.exe --metadatadir C:\AosService\PackagesLocalDirectory --bindir C:\AosService\PackagesLocalDirectory\Bin --sqlserver . --sqldatabase axdb --sqluser [sql login] --sqlpwd [sqlpassword] --setupmode maintenancemode --isinmaintenancemode false



Reset IIS/Cycle the AOS: > iisreset


Note:
The example above was for importing it into a onebox. Depending on the environment you may need to change the drive from C:\* to K:\*
For this exe we list the metadatadir as the bin folder as well
The sqluser & sqlpassword will be different for each enviornment
The database name may be different depending on the environment

D365FO - OneBox Default account information

$
0
0
It seems like you have to dig through the internet to find onebox login information so I thought I would put it on here to make it easily find-able.

OneBox default windows login:

Login: local\Administrator
Password: pass@word1

OneBox SQL login
Login: axdbadmin   
Password: AOSWebSite@123


I will add more as I run across the need for different accounts that are associated with the OneBox.

Architecture

$
0
0
Microsoft Dynamics AX has a three-tier architecture. Three-Tier Architecture Three-tier architecture is defined as having a separate database, server and client where: • The database stores the data. ...(read more)

Extended Architecture

$
0
0
Several other components of the Microsoft technology stack are used in a typical deployment. Reports are delivered by SQL Reporting Services (SSRS). SSRS is a component included in SQL Server. Business...(read more)

Introduction of Power BI integration in D365

$
0
0
In Microsof Dynamics 365 Power BI is a collection of tools and services that enables interactive visualizations and dashboards. Power BI is the tool that many users choose when they want to create interactive...(read more)

Cost Saving Capabilities on Azure for Dynamics AX 2012 R3

$
0
0
How cost savings can be possible for Dynamics AX 2012  R3 VMs? Azure Resource Manager (ARM) and classic deployment models (ASM) represent two different ways of deploying and managing your Azure solutions. You work with them through two different API sets, and the deployed resources can contain important differences. The two models are not compatible...

The Ever Green "Dynamics 365 for Finance and Operations"

$
0
0
Now we have heard so much about Ever green product life cycle for Dynamics 365 for Finance and Operations . After the latest product release, Microsoft has taken a step further towards Ever-green approach...(read more)

Change management and ERP: Understand the limits

$
0
0
It is hard to argue with a successful entrepreneur that his processes are not the primary reason for his company's success.  Not only does a business leader believe in the process, he or she may have actually authored it. Companies, whether they ...read more

#D365FO Diary 02: Time to create a comprehensive training plan for our end users, Part 1

$
0
0
Entry date : June 2018 Entry by : ERP Project Manager Entry name : Time to create a comprehensive training plan for our end users read more ...read more

D365FO - Importing License File (ISV/VAR Add-on) via deployable package into QA/Prod

$
0
0
Because we do not have the same access in QA/Production/Build as we do in the lower level environments installing a license file is a bit different compared to development, test, stage (any environment within the supplemental scope)

In order to deploy this license file to production or QA we need to do the following. It is good to note that creating this package is not environment specific. Meaning you can create this package on dev and deploy to prod or create on test and push it is QA or stage. It is just a set of pre-defined scripts which is why it doesn’t matter.

Any AOS server:

Windows Explorer > \AOSService\PackagesLocalDirectory\Bin\CustomDeployablePackage
*usually C:\AOSService\PackagesLocalDirectory\Bin\CustomDeployablePackage or on the K-drive*



In here you will find the file ImportISVLicense.zip

Make a copy of this zip file and open it up. Then browse to the following location: ImportISVLicense.zip\AosService\Scripts\License

Copy the license .txt file into this folder and save the zip.


NOTE: During my first try of this I extracted the zip, copied the file into it and zipped it back up. However during the next steps below that allow the license file to be applied I received an error message saying it has an invalid HotfixInstallationInfo.xml even though I did not touch this file. If you modify the zip directly LCS has no issues with the file so I would recommend not extracting the zip file but rather just using the default one as a template and copy the zip somewhere else and make the change there.

It is also good to note that you can put multiple license files in single package. But it is good note that it will import from alphabetically


LCS > Open the AX project in which you wish to apply the license to which in this case is the QA environment which means we need to open the implementation project. Then go to Asset library


Go to software deployable package > Click on the add button and fill out the info regarding the file being uploaded and select our zip file we created in the steps above

You will need to give it a couple of minutes before the "valid" box has a check mark. You will not be able to apply this file until the instance is marked as valid.

Once the instance has been marked as valid we need to apply it to the system.

Go to full details page for the specific environment we need to apply this to and click on the Maintain option > Apply updates




From this window we need to choose the asset we just created and click on apply



After this the system will process the request and trigger emails whenever the process starts and completes.

Whenever you open the main page you will also see the current status of the import itself as well.


From this point we can choose to either A. Do nothing and allow people to test or B. can mark the asset was as release candidate.

You should now be able to log back onto the environment  and see that the isv solution is now there

And that the license configuration page now has the license checked.


Extensible Data Security examples – Secure by legal entity

$
0
0

In my last blog, I shared some code examples for eXtensible Data Security (XDS). In this post, I will explain how it works and also introduce a V2 version which will be more advanced in determine which legal entities will be visible for the user.

Secure by legal entity

About four and a half year years ago, I already created the first version of the security policy to constrain records on the form Legal entities. At that time I did create a blog describing all steps in detail how to create this policy. You can read the blog How to restrict legal entities based on assigned organizations – AX 2012 how this policy was created.

To be able to have this version of the policy working, you should restrict all security roles; also the system user role. All other details are documented in the initial blog. There might be an additional requirement to constrain also accounting entries. This is based on global tables, but are already filtered on reports and forms within the client. However, if you want to use the Excel add-in in AX2012 with these accounting entries, there was no company (DataAreaId) context field, so it showed also data for companies which are not part of your domain. So, in addition to the explanation provided in the blog mentioned above, this has been covered in this security policy.

Enhanced version

As described above, the system user role needs to get restrictions on assigned organizations; otherwise the legal entity form shows too many records. Also, it might be the case that a person would be e.g. a sales assistant in all legal entities, but an accountant in just a few legal entities. For this purpose, I was thinking of another way to get a certain result.

I got the idea to look at all roles which does grant permissions for the Legal entities form. Then only look at the organization assignments for these roles and ignore the settings for the system user and other roles which does not have permissions on this entry point. To be able to achieve the desired result, I had to create a new so-called MyContruct table which builds a list with companies. (A MyContruct table is a special temporary table which creates a temporary table on the SQL server per user with his/her own values using a table method ‘xds()’.)

This new table has been used in a new view instead of the MyLegalEntities table in the first table.

All objects (V1 and V2) can be found on my My OneDrive DynamicsShare. Note that the provided examples of V1 and V2 cannot be used together without modifications. As they both have a policy on the same table(s) for all roles, only one policy should be active at a time.

 

If you want to explore these examples, feel free to download and use it. The software is provided as-is and you cannot obtain any rights if something is not working correctly. You have to ensure you will install the examples in a separate environment first and test it carefully. If you have questions or feedback, feel free to add comments or send a message.

 

 

That’s all for now. Till next time!

 

Microsoft Dynamics CommunitySubscribe to this blogger RSS FeedMy book on Merging global address book records in AX 2012

The post Extensible Data Security examples – Secure by legal entity appeared first on Kaya Consulting.

Dynamics 365 Achieves Broad Range of Compliance and Attestation Updates

$
0
0

In my previous blog post, I discussed Microsoft’s commitment to achieving and maintaining those certifications and attestations that support the needs of our customers. In our ongoing work to deliver on that promise, I am happy to announce that we have delivered on that commitment.

In addition, we also just achieved FedRAMP High authorization for Dynamics 365 Government. You can read more in the blog post from Kevin Briggs, Direction, Business Applications, Microsoft Federal.

Below is the list of the net new certifications and attestations that each Dynamics 365 application has achieved. You can read the complete list of certifications in Microsoft Dynamics 365 Cloud services compliance.

Dynamics 365 for Finance and Operations

  • EU Model Clauses
  • FERPA
  • HIPPA BAA
  • ISO 27001
  • ISO 27017
  • ISO 27018
  • Spain ENS
  • Spain LOPD
  • SOC 1 (SSAE 18) Type 2
  • SOC 2 Type 2

Dynamics 365 for Retail

  • EU Model Clauses
  • FERPA
  • HIPPA BAA
  • ISO 27001
  • ISO 27017
  • ISO 27018
  • PA-DSS
  • Spain ENS
  • Spain LOPD
  • SOC 1 (SSAE 18) Type 2
  • SOC 2 Type 2

Dynamics 365 for Talent

  • EU Model Clauses
  • ISO 27001
  • ISO 27017
  • ISO 27018
  • FERPA
  • HIPPA BAA

Dynamics 365 Business Central

  • EU Model Clauses
  • FERPA
  • HIPPA BAA
  • ISO 27001
  • ISO 27017
  • ISO 27018
  • SOC 1 (SSAE 18) Type 2
  • SOC 2 Type 2

Dynamics 365 for Customer Service

  • ISO 27017
  • Spain ENS
  • Spain LOPD
  • FedRAMP High

Dynamics 365 for Field Service

  • ISO 27017
  • Spain ENS
  • Spain LOPD
  • FedRAMP High

Dynamics 365 for Project Service Automation

  • ISO 27017
  • Spain ENS
  • Spain LOPD
  • FedRAMP High

Dynamics 365 for Sales

  • ISO 27017
  • Spain ENS
  • Spain LOPD
  • FedRAMP High

Microsoft Social Engagement

  • EU-US Privacy Shield
  • ISO 27017

We continue to help our customers meet complex obligations, including the EU GDPR, ISO 27001, ISO 271018, and HIPPA with the general availability of Compliance Manager, a cross-Microsoft cloud service solution, for Dynamics 365, Azure, and Office 365 Business and Enterprise subscribers. You can read more about Compliance Manager here and how it supports Dynamics 365 here.

[AX2012] How to: Set up Analysis Services and deploy cubes

$
0
0

Today I will show how to set up analysis services on Dynamics AX 2012, although it takes several steps to complete this walkthrough the process is quite simple.

Before we proceed, we need to install SSAS, which I am not going to cover in this post but you can check this link for detailed instructions.


I do recommend to check SSAS service account database privileges to Dynamics AX Business Store, if you are on a previously configured environment check the account used to run SQL Server Analysis Services (MSSSQLSERVER):

Now head to SQL Server Management Studio and make sure you service account has db_datawriter, db_datareader and db_ddladmin privileges to Dynamics AX Business Store.

061614_0956_configuring4 (1)

Installing analysis server component:

  1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components.
  2. On the Select components page:
    1. Select the Analysis Services configuration check box.
    2. Click Next.
  3. On the Prerequisite Validation page, resolve any errors. When no errors remain, click Next.
  4. On the Select a file location page, select the location.
  5. On the Specify a location for configuration settings page, specify whether you want the cubes to access configuration information from the registry on the local computer or from a shared configuration file.
  6. On the Connect to an AOS instance page, enter the name of the computer that is running the Application Object Server (AOS) instance
  7. On the Specify Business Connector proxy account information page, enter the password for the proxy account that is used by Business Connector.
  8. On the Specify an Analysis Services instance page, select an instance of Analysis Services.
  9. On the Connect to a SQL Server Database page, follow these steps:
    1. Select the computer that hosts your Microsoft Dynamics AX online transaction processing (OLTP) database.
    2. Select the Microsoft Dynamics AX OLTP database.
  10. On the Ready to install page, click Install.
  11. Click Finish to close the Setup wizard.

Open Dynamics AX rich client and head to System administration> Setup > Business intelligence > Analysis Services > System currency and exchange rate type. Confirm if you have set up System exchange rate type, if not, click on System parameters and configure it.

Set up OLAP connection:

  1. Click System administrationSetup > Business intelligence > Analysis Services >Analysis Server
  2. On Analysis server form, change OLAP server name to your server where SSAS is installed and make it default.

The last step, deploy your cube to SSAS. For the purpose of example I will deploy the forecasting cube, which is one of Dynamics AX default cubes.

On Dynamics AX rich client, click File/Tools/Business Intelligence (BI) tools/SQL Server Analysis Services project wizard.

On the Analysis Services project wizard page, click Next.
Select Deploy, click Next.

We are going to deploy a project from AOT, select Demand Forecast. Click Next.

On Deployment Options, verify which SSAS server your are deploying and change the database name if you wish. You can either deploy through AX checking Process the project after it is successfully deployed, or you can do it through SSMS, Click Next.

Finish the wizard and you are done!

If you have chosen to deploy through SQL Server Management Studio (SSMS), connect to your Analysis server database.

Right-click your database, if you have followed my example right-click Demand Forecast initial and click Process.

Click Process and wait until SSMS finishes deploying your cube and we are done!

While writing this walkthrough I faced some issues but all related to firewall and privileges problems, which SSMS gave a very understandable message error, which can be avoided by checking your SSAS account privileges like described in the start.


Model Driven Architecture(Layer)

$
0
0
Microsoft Dynamics AX is designed with a unique layer and model structure that separates and controls the updates and modifications made in the application. This structure provides a powerful and flexible...(read more)

Models

$
0
0
A model is a logical grouping of elements within a layer. Models help in situations where multiple ISV solutions or projects must operate together. This architecture allows many solutions to co-exist within...(read more)

Licensing and Configuration

$
0
0
The basic security architecture in Microsoft Dynamics AX includes license codes and configuration keys. License Codes License codes control the modules that can be used within Microsoft Dynamics AX. If...(read more)

MSDyn365FO. How to playback a task recording from X++.

$
0
0
Warmup of a VM is an old issue and everyone tries to find a workaround. It is critical for demo VMs that are turned off most of the time and you don’t want to demo a product that is slow as hell. Well...(read more)

Vendor invoice workflow – Email approval (3)

$
0
0
This webcast extends the previous one and shows you how you can incorporate a signing limit approval Matrix in MS-Flow that is used for approving vendor invoices from D365FO. In addition, you can see how...(read more)
Viewing all 17314 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>