http://blogs.msdn.com/b/crm/archive/2015/05/13/calling-all-crm-online-customers-the-annual-dynamics-product-satisfaction-survey-is-here.aspx 

The team at InterDyn BMI explains how to pay vendors with EFT payments using EFT for Payables as well as how to use Safe Pay to confirm the authenticity of payroll and accounts payable checks.

Learn more about Microsoft Dynamics GP.

by InterDyn BMI

Today I got change to work with timeedit control in Ax where we have to get input of time and then take difference to get number of hours.

For this example I used timeEdit control and add two timeEdit control in form.These timeEdit controls are unbound, I set the out of the box FromTime and ToTime extended data Type and set auto declaration property to true so these controls can be access by name in code.

Similarly set the properties ToTime.

Now add button and add its click method. The time difference between two times value can be get with timeConsumed out of the box function.

void clicked()

{

super();

info(timeConsumed(txtFromTime.value(),txtToTime.value()));

}

output is as

out put is as

Hopefully at this point you have began looking at our prior Dynamics GP 2015 Upgrade blogs that we've been releasing since April 30th, 2015:

--Microsoft Dynamics GP 2015/R2 Upgrade Blog Series Schedule

--Lifecycle for versions of Microsoft Dynamics GP: How long am I supported?

--Upgrade Planning

--Known Upgrade Issues

--Version Checks and Upgrades

If you haven't already looked through these blogs, I would highly recommend it if you are beginning to think about upgrading to Microsoft Dynamics GP 2015/GP 2015 R2.

I would also recommend looking through the 'System Requirements for Microsoft Dynamics GP 2015' page and the 'Upgrading to Microsoft Dynamics GP 2015' hot topic as well, as these will also be updated with the Dynamics GP 2015 R2 information:

>>Microsoft Dynamics GP 2015 Product Download page / Dynamics GP 2015 DVD:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/product-releases/MDGP2015_Release_Download

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/product-releases/MDGP2015_Release_Download 

>>Microsoft Dynamics GP 2015 Service Pack and hotfixes page:

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/service-packs/MDGP2015_PatchReleases

>>Upgrading to Microsoft Dynamics GP 2015 hot topic:

https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2015Upgrade

>>Microsoft Dynamics GP 2015 Upgrade Instructions guide:

https://mbs.microsoft.com/Files/customer/GP/Downloads/ProductReleases/Upgrade.pdf

Database Upgrade - The Basics!

The upgrade to Microsoft Dynamics GP 2015/GP 2015 R2 is the same upgrade process that we've had in prior versions, in that the database upgrade takes place through Microsoft Dynamics GP Utilities.The upgrade manual outlines the step-by-step process for this upgrade. Here are some of the basics.....

1. Setup your test environment so you can run a test upgrade of Dynamics GP 2015 first. This way, you'll know what, if any, errors you'll run into during the upgrade process, what it'll take to fix them, and how long the total upgrade process will take, so you can better plan on downtime the users will be out of the Dynamics GP application during the upgrade.

2. Review the upgrade manual and hot topic for the latest known issues and pre-upgrade steps and scripts. The hot topic will also tell you what build of Microsoft Dynamics GP 2015/R2 you must be upgrading to, depending on what build of Microsoft Dynamics GP that you're coming from, and whether your current build is high enough to be able to upgrade directly to Dynamics GP 2015/R2.

3. Backup your existing DYNAMICS or system database for Microsoft Dynamics GP, as well as all company databases, any modified forms and/or reports dictionary files at a minimum.

4. Obtain all the Microsoft Dynamics GP 2015/R2 product download DVD and patch files that you will need for the new version.

5. Obtain all the code and installs for any third-party or integrating products being used with Microsoft Dynamics GP.

6. Install Microsoft Dynamics GP 2015/R2 to include all features that you currently have installed on your current Microsoft Dynamics GP environment, as well as any new features the customer plans to use at the new version. If you're already on Microsoft Dynamics GP 2015, going to R2, then you will just need to apply the R2 patch on your existing Dynamics GP 2015 installs, before upgrading the databases and modified forms and reports.

7. Launch Microsoft Dynamics GP 2015/R2 Utilities and after the version check, it'll detect that you have databases that need to be upgraded, click Next through the wizard to first upgrade your DYNAMICS/system database and then your company databases after that completes.

8. When the Additional Tasks window appears, the database upgrade should be completed and successful. If the Upgrade Company window returns your company database(s) with a Red X, troubleshooting must take place as it normally means there was an issue with the upgrade of that database.

9. Upgrade any modified forms and/or modified reports dictionary files that you have, if any. The 'Modified Dictionary Upgrade' blog is being released May 19th, 2015, so look for that to find additional information on this process.

Database Upgrade Tables:

1. DU000010

The DU000010 table in the DYNAMICS/system database is the 'Utilities Update Files' table, meaning that it contains a list of tables that Utilities uses to determine which tables must be upgraded between the version/build of Microsoft Dynamics GP that you're currently on and the version/build that you're upgrading to. Not every table gets upgraded with each service pack or hotfix released, and this table helps Utilities determine just that.

2. DB_Upgrade

The DB_Upgrade table is also held in the DYNAMICS\system database and is the first table looked at when you launch Microsoft Dynamics GP Utilities. This is the main version table reviewed during the version check process discussed in the previous blog. Once the upgrade begins, Utilities will change the db_verMajor, db_verMinor and db_verBuild columns to the new version/build values that you're upgrading to. Not all features/modules in this table have the same version/build numbers nor do all features/modules get upgraded for each major upgrade, service pack or hotfix, so you may see different results for each of these. The db_status column will also change as the upgrade of the database progresses, beginning at 0 (zero) and moving up at each step, for example 23 indicates the tables conversion process is taking place and 53 is the Load Stored Procedures process with 54 being the 'wrapping up' step right before the upgrade process completes and changes the db_status back to 0 (zero). Once the database is upgraded successfully, the db_verOldMajor, db_verOldMinor and db_verOldBuild column values will be set to match those of the db_verMajor, db_verMinor and db_verBuild columns for each feature/module record, then it updates the DU000020 table.

3. DU000020

The DU000020 table is another table that holds the version information for each feature/module per database that is installed. The versions in the DU000020 table will remain at the previous release until all tables in the database have upgraded successfully and the DB_Upgrade table is showing the same version/build for both versions and the db_status is 0 (zero) again. When a user launches into Microsoft Dynamics GP it is the DU000020 table information that is looked at for the DYNAMICS/system database and all company databases. This is different from Dynamics GP Utilities, which looks at the DB_Upgrade table instead.

4. duLCK

The duLCK table is used by Utilities to put a lock on a database while it is being upgraded or used in the upgrade process. This prevents users from logging onto the database during the upgrade process and/or making any changes to it. Once Utilities has completed the upgrade of the database, it will remove the record thus releasing the lock on the database. If Utilities is shut down or closed improperly, for example if the machine reboots or Utilities is killed through Task Manager, this record may remain in the duLCK table and when you re-launch Utilities, there will be a 'padlock' symbol next to the database symbolizing that the database is locked and you'll need to close Utilities, remove this record and then re-launch Utilities again before continuing with the upgrade of this database.

5. DU000030

Lastly, is the DU000030 table, or Utilities Fail List table. When Utilities starts upgrading the tables within each database, it looks at the DU000010 as mentioned above to see what tables need upgrading. For every table upgraded, a record is inserted into the DU000030 table with a status for the upgrade. The 'Status' column shows which tables failed to upgrade and which were successful. Some common Status values for this table are:

0 - The conversion ran to completion without error

2 - The table being converted or deleted was not found

15 - The table was already converted since the table's structure matches the destination table definition.

25 - The path to the table could not be determined.

70 - Script Error. An error occurred while running a script. **Normally, this error is a result of another table causing this table to fail**

135 - An error occurred and the table was renamed back to its original name and structure containing any data within it.

***The DU000030 table, for this reason, should always be empty before you launch Utilities for the first time on an upgrade of Microsoft Dynamics GP, whether it be a major version upgrade, service pack, hotfix or any other update that changes the database version information. Before launching Utilities to upgrade the DYNAMICS/system database, make sure this table is empty, otherwise it can potentially cause errors with the upgrade by skipping tables during the upgrade process***

***NOTE: The 'Microsoft Dynamics GP 2015/R2 - Upgrade Troubleshooting' blog, being released on May 21st, 2015, will discuss in more detail how to troubleshoot errors during an upgrade of Microsoft Dynamics GP.

Server vs. Client/workstation - Where should you upgrade?

You can launch Microsoft Dynamics GP 2015/R2 Utilities from the server or from a workstation, so because of this, you are not required to install Microsoft Dynamics GP on the SQL Server. The upgrade can be launched from a server or client workstation installation. The only difference may be a slight slowdown as Utilities communicates with SQL Server back and forth, between the two machines, but this does not add much, if any, overhead however.

Upgrading all companies at once vs. one or a couple at a time:

Upgrading all company databases at the same time is recommended but doesn't make much different as far as Utilities is concerned, as it will upgrade each database in the same manner regardless. If you choose to upgrade all company databases at the same time, which is default, Utilities will run through all company databases' upgrade process, one after the other, and won't stop until either all company databases have been upgraded successfully, or an error occurs on one of the databases, that requires troubleshooting to move forward.

If you choose to upgrade one company database at a time, Utilities will upgrade that company database and then once it completes, it will go back to the 'Additional Tasks' window in Microsoft Dynamics GP Utilities and you will need to close Utilities and re-launch it in order to select other remaining company database(s) to upgrade next or it will show an error message if one should be found.

Continue to check back with our Microsoft Dynamics GP 2015 R2 Upgrade Blog Series Schedule to learn more about the Microsoft Dynamics GP 2015 R2 Upgrade!

VIDEO!! VIDEO!! >>>We are working on getting a walk through demo video of the Microsoft Dynamics GP 2015 Database Upgrade available here asap. Keep watching for it!! 

A frequently asked question we get from users using Access Teams is: How do you join or link from the account record to the users on the account team in a query? The Access Team functionality is great, but it is not easily queried from the user interface – such as through Advanced Find. So, let’s talk about how you would do this from SQL.

Understanding CRM data structure is vital in this case. From a data structure, the following tables would be utilized:

• PrincipalObjectAccess
• TeamBase
• TeamMembership
• TeamTemplate
• SystemUser

Use this SQL Query to retrieve all Access Team Members for Account(s):

SELECT     a.Name AS AccountName, t.Name AS TeamName, u.FirstName, u.LastName, tt.TeamTemplateName
FROM         Account AS a INNER JOIN
PrincipalObjectAccess AS poa ON a.AccountId = poa.ObjectId INNER JOIN
TeamBase AS t ON poa.PrincipalId = t.TeamId INNER JOIN
TeamMembership AS tm ON t.TeamId = tm.TeamId INNER JOIN
SystemUser AS u ON tm.SystemUserId = u.SystemUserId INNER JOIN
TeamTemplate AS tt ON t.TeamTemplateId = tt.TeamTemplateId
WHERE     (a.Name = ‘Test Account’)

Note: To retrieve all accounts, remove the Where Clause

Hope this comes in handy! If you need additional tips and tricks, please feel free to check our multitude of Dynamics CRM blogs.

Happy CRM’ing!

The post How to Retrieve all the Access Team Members for all Accounts in Dynamics CRM appeared first on .

Dynamics GP 2015 R2 is quick to deploy and easy to use! This latest version associates with Office 365 and Microsoft Azure to offer a powerful solution to support your business ambitions. Make your business more dynamic using this combination of ERP with productivity, collaboration and reliability. Dynamics GP 2015 is packed with new features and enhancements. The top new enhancements include:

• Self-Service User CAL – This lower-cost self-service user type is for users who only needs light functionality within GP.  The self-service user CAL is a named user applied per individual.
• Business Analyzer R7 - A tablet app available in the Windows, Android, and iOS app stores.
• Service-Based Architecture - Lower costs and the time required for customers and partners to create and modify solutions built on Dynamics GP.
• SmartList Designer & Refreshable Excel Reports - The ability to actually create new SmartLists without purchasing an add-on product to do this. If your needs are fairly simple, you need to take a look at the SmartList Designer.
• Workflow for Approvals that includes General Ledger Batch Approval, Payables Batch Approval, Receivables Batch Approval, Vendor Approval - Workflow approvals allow organizations to streamline the way they work.  Approval workflows actually came out in GP 2013 R2.  However, it was limited to purchasing.  Now you can easily set up workflows that don’t require any outside components like SharePoint.
• Expanded Workflows – Streamline financial, purchasing, sales, payroll and project expense related approvals. These new workflows allow customers to customize solutions and accelerate business approvals.
• Identity Management – Enables a single log in through integration with Microsoft Azure Active Directory to allow users to work seamlessly across Dynamics GP, Office 365 and other cloud-based apps.
• Requisition Management - The ability to use purchase order requisitions prior to actually creating the purchase order is huge for most organizations. Many companies have processes in place that are completely manual including paper trails, calls, emails. This functionality was available in the past with add on tools, but now is built right into GP. Almost every organization has purchase orders so why not build a requisition process in front of it to control whether or not we should go ahead with that purchase order.

Let us tell you about these changes so you can take advantage of them when you upgrade to Dynamics GP 2015 R2. Please call Robert McFall for more information at 901-382-1634 or email Robert at robert@3821meg.com.

by Computer Resources

Launching a web store is a great way to give your customers access to your merchandise anytime they want. They can shop at their convenience without having to leave the house. But managing a web store and all the data needed for it to run smoothly is a lot of work that can lead to many frustrations. Integrating your Microsoft Dynamics ERP to your web store relieves some of this stress and helps ensure a better user experience for your customers.

Real-Time Data

When your web store is integrated to your Microsoft Dynamics ERP, you only have to update one system. Once data is updated in Microsoft Dynamics, it pushes this information out to your web store in real time, making sure the pricing, inventory, product data and shipment dates are all accurate. Having one single source of truth reduces the chance of humor error, time spent managing multiple databases and makes sure a customer never purchases an out-of-stock or incorrectly priced item.

Spend Time on Other Areas

Focus on other areas of your web store while your Microsoft Dynamics ERP is taking care of current orders, inventory, pricing, invoices, customer profiles and payments. With online orders automatically sent to your Microsoft Dynamics ERP, you’ll have faster order turnaround and won’t be left manually entering information in separate systems. This leaves time for designing your web store’s layout and promoting it to customers. Have your web store work as hard as your Microsoft Dynamics ERP by using responsive web design. This ensures your site will work properly and look great on any web-enabled device. It’s also a best practice as recommended by Google.

By integrating your Microsoft Dynamics ERP to your web store, you’re getting twice the work done and only managing one system. By always having accurate product information on your site, your customers can shop with ease and you’ll have one less thing to worry about. Whether your site is B2B or B2C, a k-eCommerce integrated eCommerce solution will take your business to the next level. Check out our website for more information on integration and the benefits it offers. Contact our team for additional questions.

by k-eCommerce

Like any major technology deployment, ERP implementations can be extremely complex. If your ERP implementation is not managed correctly, it can cost you time and money and leave you in a precarious situation.

There are many factors that can have a significant impact on the success of an ERP implementation and selecting the right implementation partner is high on the list. Picking a partner is about finding a company that is competent, reliable, a good fit for your business expectations and an expert in change management.

Consider these three issues as you search for the right implementation partner:

1. Rethink Multi-Sourcing—Many companies have resorted to hiring multiple experts in an attempt to get product, business, industry, and change management skills for their project—a practice called multi-sourcing. While this practice can be effective for some companies, it is important to understand that multi-sourcing adds management and delivery complexity to your project. Instead, look for an implementation partner with professionals who understand the nuances of your industry and its processes, and who can craft a solution for that industry or extend the solution if gaps exist.

1. Look for a Partner Who Offers Innovative Solutions—ERP software solutions enable visibility throughout the entire organization, allowing decision makers to make better decisions and employees to be more productive.

1. Take a Long-Term Approach—Embracing your implementation partner as a long term part of your team can help ensure your success down the road. If your ERP partner is dedicated to a long-term relationship, you will reap the benefits of a successful ERP implementation—and a technology alliance that will serve you for many years to come.

ERP implementation is a challenging process which, upon successful completion, will affect most aspects of your business. ERP partners should be 100% vested in making your project a success and committed to a long-term partnership.

As a national Microsoft master VAR (Value Added Reseller) and Gold Certified Partner, SBS Group can help you fully optimize your ERP functionality and workflows to elevate your business processes, improve the utilization of data throughout your organization, deliver ongoing training and support resources, and more.

Contact us today for more information on how SBS can be your strategic partner, or follow us on LinkedIn at http://www.linkedin.com/company/sbs-group, on Twitter at http://www.twitter.com/sbsgroup and find us on Facebook at http://www.facebook.com/SBSGroupUSA.

by SBS Group

This is part 3 in our Azure Partner Community blog series about adding Microsoft Dynamics CRM Online to your practice. Read part 1 and read part 2.

How to get started with Microsoft Dynamics CRM Online in your Azure practice

If you’ve made the decision to add Microsoft Dynamics CRM Online to your Microsoft Azure practice, this post will provide you with the guidance you need to take the next step and get started.

The US Dynamics CRM Online Partner Portfolio Recruitment team (Dynamics PPR) is your first connection to start your planning. Each Recruiter is geographically based, and has an Operations resource that is dedicated to helping partners through the onboarding process.

Azure partners typically have a line of business focus or custom application development focus in their CRM Online practices, as opposed to a more traditional Sales Force Automation focus. The Dynamics PPR team can discuss with you how to extend your business to include a Dynamics CRM Online practice that will drive great customer experiences. We refer to these areas of focus—line of business and custom application development—as xRM focused Dynamics CRM practices.

Once you are connected with the Dynamics PPR team, your Recruiter and the Operations resource will work with you and your team to go through the operations onboarding process. We use a variety of tools and phone-based meetings to help you complete the steps.

In addition to the operational considerations of starting your CRM Online practice, your Recruiter will schedule regular calls that will help you:

• Develop the CRM Online portion of your cloud business plans
• Review your go-to-market strategy
• Enable field engagement when appropriate
• Strategize on sales cycles
• Initiate partner to partner connections
• Inform and remind you of key events and CRM /xRM announcements and news
• Share best practices from successful Dynamics CRM Online partners

An example of partner-to-partner connections is making you aware of Dynamics CRM Online ISVs that have developed solutions that consume Azure but do not resell Dynamics CRM Online. These ISV solutions offer growth opportunities for your Microsoft CRM practice.

Also part of each Recruiter’s virtual team are Dynamics CRM Online Solution Architects, who can offer technical guidance about how Azure and CRM Online can work together in various scenarios. A significant area of opportunity for Azure partners is enterprise deployments of Dynamics CRM on Azure, as those often require an internal or external facing portal of some form. CRM Online and xRM solutions can utilize a variety of Azure features, like Compute, Websites, Storage, Database, and others. CRM Online also uses Azure Active Directory. Azure AD Premium provides tools for enterprise CRM deployment such as Self Service Password tools, Multi-Factor Authentication, Active Directory Write-Back, and 99.9% SLA. The team and tools are in place to help you ramp quickly and incorporate Microsoft CRM Online and xRM into your Microsoft Azure Cloud Practice.

For more about xRM, download the presentation from our Azure Partners Yammer group.

Connect with the Dynamics PPR team today

To connect with the Dynamics PPR team, email nominatepartner@microsoft.com. A Dynamics Partner Portfolio Recruiter will respond and follow up with you to discuss your interests as well as provide further details about becoming a successful Dynamics CRM Online partner.

In the Microsoft Azure Partner Community blog series and call for May, we’ll help you learn more about CRM Online and understand why you should consider investing in adding it to your Azure practice. Register for the May 21 community call. Our next blog post in this series will talk about the vision for CRM Online with Azure.

CRM Online partner resources

• Microsoft Dynamics CRM Online on the partner portal
• Partnership journey with Microsoft Dynamics CRM Online
• Cloud SureStep for Microsoft Dynamics CRM Online
• Microsoft Dynamics Cloud Partner Profitability Guide
• Internal use rights guide for Microsoft Dynamics CRM and CRM Online
• Recommended training for Sales, Marketing, and Technical roles
• Modern Biz | Microsoft Dynamics CRM Online marketing campaign

CRM Online product information

• Test Drive Microsoft Dynamics CRM
• Product release information for Spring 2015
• Microsoft Dynamics CRM pricing and licensing

Are you a Microsoft Dynamics CRM, Microsoft Dynamics Marketing, Microsoft Social Engagement, or Parature customer? Your mission is to contribute to the future of these products.

To accomplish the challenge, please stop reading this blog for 20 minutes, and answer the call from CRM team.

If you are both a customer and a partner, say you are a customer otherwise you will receive an immediate “thanks but no, thanks” page.

You have until May 18, 2015 to complete the mission. Good luck.

Since a couple of years codeunits have a property called Subtype. Selecting a specific value for this property changes the behavior of the codeunit, one of them being an extra property added to functions, i.e. FunctionType (for Test Codeunits and Upgrade Codeunits) which defaults to a specific value depending on the Subtype value (see my post NAV 2015 Glance 4: New Functions are Local by Default?).

Now what happens when you change the Subtype of a codeunit? As FunctionType values depend on the codeunits Subtype C/SIDE cannot just leave the FunctionType as is. Let's try and see.

Scenario 1 - Changing a Test Codeunit to Normal

So we create a test codeunit with a test function:

And change the Subtype to Normal:

Now C/SIDE removes any test artifacts that do make sense in a normal codeunit:

Scenario 2 - Changing a Upgrade Codeunit to Normal

Let's do the same with a Upgrade codeunit:

I.e. change the Subtype to Normal:

Logically as the in previous case, C/SIDE removes any upgrade artifacts that do make sense in a normal codeunit:

This perfectly makes sense ... but for one fact: why aren't the functions set to local as is the default behavior in NAV 2015? I would prefer that as I wouldn't want any previous test or upgrade function being exposed outside of this codeunit by default.

What do you think?

BTW

Never observed this before, but this looks somehow awkward, doesn't it: Subtype v.s. FunctionType? Why is the first having a low cap t and the second upper cap T?

Link Microsoft ufficiale su MSDN (https://msdn.microsoft.com/en-us/library/jj672920%28v=nav.80%29.aspx)

Prerequisiti

Prima di iniziare l’installazione, assicurarsi di avere attivo il windows firewall e di aver installato Power Shell 3.0.

Verificare che l’utente che si sta utilizzando si possa loggare in NAV

Avvio installazione

Dalla cartella di installazione di NAV 2015 eseguiresetup.exe

Selezionare Aggiungi o rimuovi componenti

Selezionare Componenti server Web

Inserire i parametri richiesti

inita l’installazione aprire IIS per verificare il funzionamento e cambiare eventuali setup (Porte, Autenticazione, Application Pool etc.). Nel mio caso ho cambiato la porta in default da 80 a 82 (localhosts:8082)

Qui si trova l’installazione della virtual directory linkata alla NAV Server Instance e dell' application linkata all' application pool

Per testarne il funzionamento cliccare su Esplora :8082 (http)

NAV Web client:

NAV Tablet Client Emulator:

occorre poi scaricare la APP da dagli store ufficiali (es: Apple APPS Store) per utilizzarlo in modalità APP.

Parametrizzazione finale, aprire la cartella del sito web:

Nel file web.config si trovano i parametri di setup da modificare se necessario

Aprire con notepad (o vostro text editor) per modificarli:

Qui si può indicare anche la Company di default:

Verficare corretta corrispondenza con l’instanza NAV server

DEPLOY MULTI COMPANY SITE

Il sistema è già multi company By Design,

oer usare più società via web, utilizzare questa sintassi, aggiungendo la company in coda alla chiamata

http://localhost:8082/DynamicsNAV80/WebClient/tablet.aspx?company=CRONUSTEST80

http://localhost:8082/DynamicsNAV80/WebClient/?company=CRONUSTEST80

CREAZIONE SERVIZI WEB AGGIUTIVI

link MDSN https://msdn.microsoft.com/en-us/library/jj551747%28v=nav.80%29.aspx

Se sul pc/serverè gia presente un servizio web, utilizzare la procedura sottostante per crearne altri: 

Aprire"Microsoft Dynamics NAV Administration Shell come amministratore" (importante!!!)

Esempio di creazione di nuova istanza web:

New-NAVWebServerInstance -WebServerInstance WebApp2015 -Server THINKCALIGARA -ServerInstance WEB80

Corrispondenza con l’istanza server:

In IIS troviamo l’istanza web creata; con Esplora andiamo nella cartella del sito per verificare il file web.config:

Controllare la porta:

Testare

POWERSHELL COPY COMPANY TIP:

Duplicare una Company da Powershell (per chi non sapesse come si fa):

Copy-NAVCompany -ServerInstance DynamicsNAV80 -SourceCompanyName 'CRONUS Italia S.p.A.' -DestinationCompanyName 'CRONUSTEST80'

HAVE FUN !