Skip to main content
Insert Banner Message here.

Community

Search

Welcome to Community

trigger can not be deployed

Answered

Comments

3 comments

  • Kevin N

    Hi James,

    This is expected behavior. Vault checks for various restrictions when code is uploaded for deployment and will fail deployment when non-allowed code is included. The Vault Java SDK debugger does not enforce these restrictions.

    You can find more information at https://developer.veevavault.com/sdk/#restrictions. 

    While developing Vault Java SDK code, you must keep these restrictions in mind and validate your code frequently. Code that does not respect these restrictions will not be able to deploy into vault and will need to be fixed prior to being used.

     

    Thanks,
    Kevin

    0
  • James Huang

    Thanks Kevin

    0
  • James Huang

    By the way, this means that it is not possible to user a trigger to auto set up a ID field sequentially. for example, if I created a organization 1, 2, 3 and would like to have the Org ID field populated automatically by 1, 2, 3, this is not possible to use before trigger. Any other suggestions?

    Thanks

    James

    0

Please sign in to leave a comment.

Powered by Zendesk