Primavera SDK Excel File to import / export data

Even Oracle stop supporting the Excel File to import / export data, sometimes we still need to use it.

The latest version it can support is P6 version 8.3

You can download it here:

https://drive.google.com/open?id=0ByHnieTJNwKGRGpoMnJBS25HU28

Advertisements

Author: Khuong Do

Khuong Do is a Project Planner in Civil, Transportation and Oil & Gas Industry. He has worked as a Primavera Consultant Specialist since 2006 . He holds a Civil Engineering degree and a Bachelor of Information Management System. Now he is working in Petronas RAPID project, one of the biggest Refinery and Petrochemical complex, in Pengerang – Malaysia.

15 thoughts on “Primavera SDK Excel File to import / export data”

  1. Should this download Files be in a specific folder?
    Is the Username and Password the same as what I use when I to open Primavera?
    Kind Regards – AJ

    Like

  2. I have EPPM v8.3 and Office 2013 (64 bit) on my current system that have Windows 7 (64 bit).

    The question is that how can we utilize or get advantages of SDK and where exactly we are suppose to save these files in order to successful integration with P6 database. Moreover, what bit system does this SDK files have 32 or 64bit?

    Like

  3. Hi,

    my query might be OOT.

    but i having trouble on importing xml file from primavera version 16.1 to primavera version 15.2

    the error message :
    Microsoft.Practices.Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module ‘CommandLineModule’.
    – The exception message was: Exception has been thrown by the target of an invocation.
    – The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=15.2.0.15383, Culture=neutral, PublicKeyToken=null
    Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.
    —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
    at Primavera.Mercury.Importer.ImportService.DoMatchItems[TEntity](EntitySet`1 target, EntitySet`1 source, Dictionary`2 options, Dictionary`2 primaryKeyMapping, ImportProjectSettings importProjectSettings, ILoggerFacade Logger)
    at Primavera.Mercury.Importer.ImportService.ImportOneEntitySet[TEntity](EntitySet`1 source, IVenusDataServiceContext targetContext, ImportOptionsList options, ImportProjectSettings importProjectSettings, ILoggerFacade Logger)
    — End of inner exception stack trace —
    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    at Primavera.Mercury.Importer.ImportService.ExecuteImport(EntityContext sourceContext, IVenusDataServiceContext targetContext, ImportOptionsList options, ImportProjectSettings importProjectSettings, ILoggerFacade Logger, Dictionary`2 initialKeyDictionary)
    at Primavera.Mercury.CommandLineModule.ExecuteImportExport.DoImport()
    at Microsoft.Practices.Prism.Modularity.ModuleInitializer.Initialize(ModuleInfo moduleInfo)
    — End of inner exception stack trace —
    Failed to load type for module CommandLineModule.
    Error was: An exception occurred while initializing module ‘CommandLineModule’.
    – The exception message was: Exception has been thrown by the target of an invocation.
    – The Assembly that the module was trying to be loaded from was:Primavera.Mercury.CommandLineModule, Version=15.2.0.15383, Culture=neutral, PublicKeyToken=null
    Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem.

    Appreciate if anyone can share your experience.

    thanks

    Like

  4. Does anybody need such complicated tool for version 15 or 16 (64bit)? interested in a commercial need for such a tool.

    Like

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s