Microsoft Dynamics SL

Blog Post: Dynamics SL and Windows 8

Butch Adams — Wed, 19 Jun 2013 17:14:00 GMT

Quick reminder: If you have been thinking about purchasing extra users for SL or GP, time is running out to take advantage of the excellent discount Microsoft is offering. Orders must be placed by COB Friday, June 21^st.

SL and Windows 8

I have grown to love Windows 8 after getting used to how it works. I can really miss it when I jump around on machines with the older operating systems now. I guess it is a good thing it is growing on me because it is getting harder and harder to find a new machine with Windows 7 on it. (Not to mention Windows 8.1 has been announced for delivery this year.)

That said, there are a couple of considerations for SL if you have new computer purchases in your near term budget. The only supported version of Dynamics SL for Windows 8 is 2011 with SP1 or FP1. Windows 8 will need to have .NET 3.5 turned on in the Programs and Features panel and .NET 3.5 SP1 applied through Windows Updates. In addition, this work-around might be the last step you need to complete to get SL running on Windows 8.

Dynamics on Azure

NAV and GP are now available on the Azure platform. Check with your partner for more information or read the community blog about it. SL and AX are coming, but the current best info is “some point in the future.”

Under the Hood

I get asked a lot about what table in the database a certain field is in. As a bonus to those that are still reading this far into the post, here is the query to find that out. Let’s say that I want to find tables where PONbr is found:

USE SLApplication — Use your application or system db name here

Select TABLE_NAME From INFORMATION_SCHEMA.COLUMNS Where column_name = ‘PONbr’

This is a great way to get a list of tables to choose from when writing reports or using the Quick Query module but it is only helpful if you know the column name. If you need to go fishing for a column, say, I need a column related to sales tax I could run the query:

Select TABLE_NAME, COLUMN_NAME From INFORMATION_SCHEMA.COLUMNS Where column_name Like ‘%Tax%’

And scan the result list to find interesting possibilities for our reporting.

Butch Adams
Managing Consultant
Conexus SG
Dallas, Texas

Forum Post: RE: Please Tell me the tables for open Items of Customers

Butch Adams — Wed, 19 Jun 2013 15:56:00 GMT

Take a look at the various reports in AR. Which ever one returns similar data to what you are after, open it in Crystal and take a look at the tables and views it uses.

You're probably looking for something in ARDoc, ARTran or ARHist though.

Forum Post: RE: ask - field shipconfirmqty

Butch Adams — Wed, 19 Jun 2013 15:39:00 GMT

Run this query:

USE SLApplication -- Use your application db name here

Select TABLE_NAME From INFORMATION_SCHEMA.COLUMNS Where column_name = 'shipconfirmqty'

Forum Post: RE: System Error 5003 (4060)

Butch Adams — Wed, 19 Jun 2013 15:32:00 GMT

You've just about stumped the panel then ... Have you tried doing the install by doing a "Run as Administrator"? I have also corrected installation problems by just running SL the first time as administrator. If you haven't done that it would be worth a shot.

Forum Post: RE: Import data using web services

Bob Titular — Wed, 19 Jun 2013 00:39:00 GMT

Blaine, I found the problem. It's related to the mapping issue on a windows 8 workstation. After manually mapping my network share, I was able to resolve the Win32Exception error message. Here's the link that I used:

community.dynamics.com/.../having-trouble-installing-microsoft-dynamics-sl-on-windows-8.aspx

Forum Post: RE: RMS Replenishment Module

Blaine Bryant — Tue, 18 Jun 2013 21:32:00 GMT

Ian3005,

It looks like you may be working with a module that is not supported in this forum.

Blog Post: Connector for Microsoft Dynamics V3 released today

Dynamics CPM Team — Tue, 18 Jun 2013 19:45:00 GMT

Connector for Microsoft Dynamics V3 (3.0.217.1) released today! This release includes a major update to the MSDI database and Connector for Microsoft Dynamics service, designed to improve efficiency of the service as well as making it easier for customers and developers to interact with it. This release also addresses some of the key suggestions that you have given us regarding your V2 RU 3 deployments. Additional features and updates are listed later in this post.

Release Highlights FAQ:

Is it possible to save filters with my map(s)?
1. Yes, with version 3, filters are saved with maps and are included when creating a map from a file that has a filter
Do I have to always stop and restart the service every time I want to delete something or update the “Check for data modified after” time?
1. No, stopping the service with every change isn’t required in version 3
Can a developer directly interact with the service, say to change settings, create maps, or immediately force a map to run?
1. Yes, developers have more flexibility in how they interact with the version 3 service
Has the MSDI database schema changed at all?
1. Yes, please be sure to backup your MSDI database before upgrading in the event that you need to roll back to a previous version
Are the Connector for Microsoft Dynamics configuration settings still stored in the MSDI database?
1. No, they have been moved to the ConnectorServiceHost.exe.config file in the Connector’s installation directory

Feature list (all of the features listed for all previous releases are still included):

Filters are now saved with maps and are imported when creating a map from a file that has a filter saved in it
When deleting an integration, site, or map the service no longer needs to be stopped and restarted
When changing the “check for data modified after” date for a map, the service no longer needs to be stopped and restarted
Connector for Microsoft Dynamics service is now a WCF service that is run inside of its own process host, allowing developers to programmatically interact with the service
Maps can now be run “on demand” using the “RunMapNow()” API on the updated Connector for Microsoft Dynamics service. Stay tuned for a blog post demonstrating how to do this programmatically.
System handle counts and memory consumption have been reduced for long running integrations
Connector for Microsoft Dynamics client responsiveness has been improved
Performance when integrating to Microsoft Dynamics CRM online has been increased
The MSI now validates the SQL server version, as well as the other system requirements
“Socket Connection was aborted” errors when integrating using WCF services are now avoided

Release notes:

Supported Microsoft SQL Server versions have changed slightly:
- Microsoft SQL Server 2005 SP4
- Microsoft SQL Server 2008 SP2
- Microsoft SQL server 2008 R2
- Microsoft SQL Server 2012
Supported Microsoft Windows Server versions:
- Microsoft Windows Server 2008 SP2
- Microsoft Windows Server 2008 R2 SP1
- Microsoft Windows Server 2012
Connector for Microsoft Dynamics client no longer communicates directly with the MSDI database, rather it communicates exclusively with the Connector for Microsoft Dynamics service. This means that if you stop the service, the client will stop working as expected and must be closed and restarted after the service has been restarted. It also means that the ability to interact directly with the service from the Connector for Microsoft Dynamics client has been removed.
After upgrading an existing Connector for Microsoft Dynamics installation to V3, you will need to re-enter the passwords that are listed in the adapter settings for the default settings and in the “Settings” node for any integrations that you created in a prior version of Connector for Microsoft Dynamics
If you create new custom adapters using the Connector for Microsoft Dynamics SDK, after deploying those adapters to a V3 system you will need to restart the Connector for Microsoft Dynamics service (be sure to close the client first) to detect the new adapter on the system, with previous versions this restart was not required
While we have made every effort to make the upgrade process as seamless as possible, we still encourage you to test the upgrade in a non-production environment first to ensure that all of your customizations continue to work as expected before moving the upgrade into production.

Note: if you are using Microsoft Dynamics CRM Online or are planning on upgrading your on-premises deployment to the update rollup 13 update for Microsoft Dynamics CRM 2011, you will need to continue to use the classic forms for the Account, Contact, and Sales Order entities and ensure that the Connector for Microsoft Dynamics solution you have loaded in Microsoft Dynamics CRM 2011 is at least version 1.0.1603.3.

To download this release for your Microsoft Dynamics ERP system, go to CustomerSource:

Connector for Microsoft Dynamics AX

The XPO that is required to enable support within Microsoft Dynamics AX 2012 requires that Cumulative Update 1 for Microsoft Dynamics AX 2012 be installed
The XPO that is required to enable support within Microsoft Dynamics AX 2012 R2 is different than the XPO for Microsoft Dynamics AX 2012 and is listed as a separate download
Microsoft Dynamics AX 2012 R2 CU 1 is fully supported

Connector for Microsoft Dynamics GP

This version no longer supports new integrations using Microsoft Dynamics GP 10.0, upgrades to existing integrations using Microsoft Dynamics GP 10.0 are supported
All versions of Microsoft Dynamics GP 2010 and GP 2013 are still fully supported as either new or existing integrations

Connector for Microsoft Dynamics NAV

This version requires Microsoft Dynamics NAV hotfix 2597312 and hotfix 2721512 when integrating Microsoft Dynamics CRM with Microsoft Dynamics NAV 2009 R2

Connector for Microsoft Dynamics SL

Would you like to know more? Check out the User Guide for your ERP system and begin your installation preparation. I know, I know; reading documentation can be arduous. But you know what they say: an ounce of prevention is worth a pound of cure. So read the provided documentation to avoid the common mistakes and save yourself the support call. The user guides for all of the ERPs have been updated for this release and all include a V3 upgrade sections that you should be familiar with before upgrading your existing integrations. All of the known issues documents have been updated as well so please have a look at those too, they can all be found on the Connector for Microsoft Dynamics download pages.

Connector for Microsoft Dynamics User Guides

Blog Post: System Message 9851 when logging into SL

Adam Leonard — Tue, 18 Jun 2013 14:31:00 GMT

If you receive this error logging into SL, check to ensure you're not out of disk space. Another recent case pointed to the possible presence of a virus or malware on the workstation. Free up disk space on the workstation by removing unneeded files and applications then browse to the user profile and delete their .xml files (typically: C:\Users\<UserID>\AppData\Roaming\Microsoft Dynamics SL\MenuCache)

Forum Post: RE: PVREC.exe has stopped working

Chris McCoy — Tue, 18 Jun 2013 13:37:00 GMT

Oh...duh,,,thanks :-)

Forum Post: RE: HELP - Invoice not listed in Payment Application, but show in Customer Activity

rodi — Tue, 18 Jun 2013 10:12:00 GMT

hi, thanks very much.

Forum Post: RE: Where to find the schedule date Application Server items will be processed?

Butch Adams — Mon, 17 Jun 2013 21:13:00 GMT

See if AppSrvRequest in the system db has what you need.

Forum Post: RE: Management Reporter Errors ("No endpoint listening" and "You don't have permission")

Brian Meagher — Mon, 17 Jun 2013 20:19:00 GMT

As an update to this: first - Microsoft should NOT require that a particular user be logged in to deploy an application (assuming the logged in user has sufficient privileges). Or, if that is a requirement, the User Interface should show the logged in user's name in the dialog box, clearly indicating that the user will be used for the Service Account.

The update: The message about "no endpoint" seems to be something of a red herring. It seems like the installer is testing to make sure TCP port 4712 is available. Farther down in the log (in my case) was a message "an error occured during decryption". In my case, the cause was an invalid "Master Key" in the instance of SQL Server I was installing to. Looking up error "Msg 15466" in google lead me to the answer: forcefully reset the Master Key for the instance of SQL Server. Look for articles referencing ALTER SERVICE MASTER KEY to learn more.

Very specifically in this case, I believe that the instance of SQL Server was originall built, and then the master database was restored from a different instance to retain security and other configuration data.

Bottom line: Microsoft needs to work on the MR installation/configuration tool to provide MUCH better error reporting for things that seem to be pretty common in the field.

Forum Post: RE: Incorrect Payment amount

Carolyn Kolpien — Mon, 17 Jun 2013 17:27:00 GMT

Hi KDYoung,

You can go back into the Application Inquiry Reversal screen and select the Void Application option. This will void the payment and update the GL accounts that were affected by the initial payment batch. There is no way to correct the payment amount after the batch is released. Your other option is to enter a debit memo, apply the payment to the debit memo, and reenter the payment correctly. You will not be able to use the same payment number as the original payment.

Let me know if you have any questions.

Forum Post: RE: Message 10061 Inconsistency between grid and memory in SO Duplicate Order

Deb Lashua — Mon, 17 Jun 2013 14:08:00 GMT

Yes, that is what we ended upo doing. We were hoping to figure out why this occurred so that we could prevent it in the future. Thank you.

Forum Post: RE: SL 7 Inventory Shipped Not Invoiced

Deb Lashua — Mon, 17 Jun 2013 13:01:00 GMT

This resolved the issue.

Forum Post: RE: Need help find info in tables for sql query.

Nam Dang — Mon, 17 Jun 2013 04:56:00 GMT

Itemsite table

Forum Post: RE: What does the whseloc field in ARtran mean ?

Nam Dang — Mon, 17 Jun 2013 02:32:00 GMT

I have one customer setup like others but all payments come from CA was post in whseloc 07 and it is devided in many line, I don't apply it with any invoices or debit, just finish it in payment application screen. I don't know the reason of this problem, can someone help me.

Thanks all

Forum Post: RE: error 10232 when copying text and after printing

Blaine Bryant — Fri, 14 Jun 2013 21:56:00 GMT

The first thing I would like to try to do to fix this problem would be to sync ownership and security in the update tab of DB Maintenance. In case you do not know how to do this the steps are as follows (It is best if no one is logged into SL while performing this):

1. Click Start > Control Panel > Administrative Tools > Microsoft Dynamics SL Database Maintenance

2. Make sure the SQL Server Name textbox has the correct server displayed

3. Login

4. Go to the “Update Databases” tab

5. In the pane on the right select “Synchronize All Ownership & Security”

6. Make sure all users are logged out of SL

7. Click the “Update Database” button

After this is completed try to recreate your error and then send me a Screen shot of any errors received.

Blog Post: Using non-printing columns in column calculations

Dynamics CPM Team — Fri, 14 Jun 2013 16:44:00 GMT

When using non-printing columns in your column calculations be sure to think about the columns you want included in the calculation. If you define range calculation, only the printing columns are included in the calculation. If you define each column individually in the calculation, printing and non-printing columns are included in the calculation.

In the screen shots below, you can see the differences in a range calculation versus individually defining each column in the calculation.

Column definition:

Report results:

Forum Post: RE: Unable to save changes to AR Customer Maintenance

pstgeorge — Thu, 13 Jun 2013 23:08:00 GMT

I have been able to duplicate this in Demo APP60... Anyone fine a solution yet?? I plan to run profiler to see if anything comes of it.