Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When naming solutions and streams, ensure that unique names are used. The maximum length of a Solution name and a Function name is limited to 30 characters, and the maximum size of the Stream name is limited to 63 characters. When a function is used multiple times in a stream, each function node receives a unique name by appending copy numbers to each consecutive node (Solution and stream names must be unique. When you duplicate a stream, '(Copy)' will be added to the end of the name to show it's a duplicate. Stream names can be up to 63 characters long, and you can rename them by clicking on the name itself in the stream view.

Note!
Duplicating a stream with a 63-character name will cause a 'bad request' error.

Function names must also be unique - when they’re duplicated within a stream they will be assigned a unique name with a copy number in parenthesis, for example, if the Count function is used multiple times, the consecutive functions are named Count (1), Count (2), and so on).  

Note
titleNote!

When a user tries to duplicate a stream with a maximum number of characters in its name, that is 63, it results in a "bad request". If the stream name does not have the maximum characters when it is duplicated, the duplicated stream name is appended with "(Copy1)".

Character restrictions apply to user input fields in Usage Engine. The character restrictions in Usage Engine apply to account names, solution names, stream names, and node or function names. You can only use the following characters when naming:Function names can be up to 30 characters long and can be edited by clicking on the name itself.

Accepted characters in name fields

The following characters are accepted in Usage Engine’s name fields.

  • Alphanumeric (a-z, A-Z,   0-9)

  • Space ( [space] )

  • Dash (   -   )

  • Underscore (   _   )

  • Round brackets

    Parenthesis (

     

    ()

     

    )

  • Period (

     

    .

     

    )

...

 

Note!

The order

...

of columns in a CSV file

...

may not always match what you set in a function. For example, in a Map processor or Amazon S3 forwarder, if

...

your headers include both numbers and letters, Usage Engine will place numeric headers first, followed by alphabetical

...

ones.