Installing customizations with .cnk

(0) Share

Report

Posted on by erowden

727

I have 4 files from a vendor with customizations to dynamics gp 2010. I need to try install these into gp2013. I have 4 files - Build Chunk.mac, .cnk, develop.dic, extract.dic. I have worked with a .cnk before when installing PSTL, but not sure what I need to do with the other 3 files and what the procedure would be.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Jonathan Fear on at

Like (0)

Report

Have you reached out to the person who built this customization? There are many different ways you make a customization. For example you can put everything in the CNK file and then when it is extracted everything that is needed will be put in the folder.

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

It would be quite difficult to assess the possibilities of your customization. Jonathan is putting things on the exact track, you do need to get back to ones who initially built the integration to give you the proper advice.

Your feedback is highly appreciated,

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi Liz,

These files are very common when packaging a dexterity application.

I will list them in order of creation and what each file represents:

1. develop.dic = The development dictionary (you will do nothing with this during installation)

2. extract.dic = This is the dictionary that is created when the dexterity developer moves the resources out of the development dictionary for packaging into the .cnk (do nothing during installation.

3. .cnk file = This is the only file you will be copying into you GP2013 folder and if it's compatible will ask you to include new code upon launching GP.

4. Chunk.mac = This is the macro that automatically runs the keystrokes for all of the steps to create the .cnk file in Dexterity Utilities (do nothing during installation).

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report

Liz,

I have to agree with Mahmoud and Jonathan on this one. The developer should have provided detailed instructions on how to deploy their customization. The first step in any installation is to review documentation - if you haven't received any, you should request some. Sometimes a developer will include a ReadMe.rtf or txt file with their code, perhaps you overlooked a file?

That being said, you should start by making a backup of the workstation folder (copy the GP 2013 folder) and any GP related SQL Databases prior to installing any customization. Most customizations modify the workstation code, and some change SQL tables on the server. You also need to ensure you have exclusive access to Dynamics GP - no other users should be in GP during the installation process. Make sure you are using an Active Directory account with administrative access and log in as the SA account into GP.

Typically you need to copy the chunk file (.cnk file) and other files provided by your developer into the workstation folder. This is the GP 2013 for Dynamics GP version 2013. When starting Dynamics GP after copying the .cnk file into the workstation folder, you should run GP with elevated privileges (as administrator). Great Plains will prompt you to include new code (this is how a chunk file is deployed), so say yes to this.

The presence of a .mac file indicates there is likely a macro to run, which may complete some critical setup steps after install - sometimes developers include .sql files, which serve similar purposes, but you didn't seem to have any of those. Once you've deployed the chunk/.cnk file successfully, go to Tools > Macros > Play and browse to the .mac file.

The only likely deviation from this approach to the install, is the .dic files may need to be in the Data folder located in the GP 2013 folder, but I would only try this after trying the approach outlined above.

Remember - the developer should have detailed instruction on how to deploy their code, and I would strongly recommend contacting them. If you have a test system, I would try the new code there first. We do User Acceptance Testing prior to rolling out any code in the live environment.

Was this reply helpful? Yes No