SDK Document Creation, with environment

Hi Group

I'am using the SDK kit to create folders and documents, which works fine, even in VB.NET. But i'am not having any luck in setting the environment name.

Normaly when you create a folder it inherit the environment settings from the parent folder, but it doesn't seem to be the issue when i'am creating folders with the SDK kit.

Is there a way to assign an environemt to a folder an a document. The other solution would be creating the information in the SQL database manually doesn't sound appealing :-)

Thank a'lot in advance

Michael

Parents
  • You can do it with aaApi_CreateProject2().  You can also do it after you create it with one of the "project" modify functions.  Keep in mind that in the ProjectWise SDK documentation, for legacy reasons, that "folders" are referred to as "projects" and "vaults" and that "projects" are actually folders too.  "Projects" in ProjectWise are referred to as "rich projects" in the documentation.

    HTHs

    PS - I forgot to mention that you really, really shouldn't attempt to modify anything directly in the database.  Always use the APIs.  The only exception would be, and is commonly done and is OK, is to update rows in your environment tables for only the user attribute columns.  This is one of the reasons why there is the "Create attribute records upon document creation" option for environments.  It allows you to "snyc" some of your user attributes with other systems via SQL based procedures, etc.  Don't attempt to create or delete rows from the environment tables without using the APIs!

Reply
  • You can do it with aaApi_CreateProject2().  You can also do it after you create it with one of the "project" modify functions.  Keep in mind that in the ProjectWise SDK documentation, for legacy reasons, that "folders" are referred to as "projects" and "vaults" and that "projects" are actually folders too.  "Projects" in ProjectWise are referred to as "rich projects" in the documentation.

    HTHs

    PS - I forgot to mention that you really, really shouldn't attempt to modify anything directly in the database.  Always use the APIs.  The only exception would be, and is commonly done and is OK, is to update rows in your environment tables for only the user attribute columns.  This is one of the reasons why there is the "Create attribute records upon document creation" option for environments.  It allows you to "snyc" some of your user attributes with other systems via SQL based procedures, etc.  Don't attempt to create or delete rows from the environment tables without using the APIs!

Children