Remus Avram

Members
  • Content Count

    489
  • Joined

  • Days Won

    13

Posts posted by Remus Avram


  1. Hi Ftrack Team,

    the component name is not unique. We are able to create components on a AssetVersion type with the same name.

    Code example:

    import ftrack_api
    
    session = ftrack_api.Session()
    unmanaged_location = session.query('Location where name is "ftrack.unmanaged"').one()
    version = session.query("AssetVersion").first()
    
    version.create_component(
            "/path/to/a/file.txt",
            data={'name': "main"},
            location=unmanaged_location
            )
    session.commit()
    
    version.create_component(
            "/path/to/a/file.txt",
            data={'name': "main"},
            location=unmanaged_location
            )
    session.commit()

    Ftrack Version: 3.5.21.4617


  2. Hi @vitek

    which version of ftack-api and ftarck server are you running?

    The example below works for us:

    import ftrack_api
    
    session = ftrack_api.Session()
    
    task = session.query("Task where name is cacatcacat").one()
    note_category = session.query("NoteCategory where name is 'Internal'").one()
    content = "this is just a test"
    user = session.query("User where username is '<username>'").one()
    
    note = session.create("Note",
                          {
                              'category': note_category,
                              'content': content,
                              'author': user
                          })
    
    task['notes'].append(note)
    session.commit()

    Can you assert all the returns?


  3. Hi,

    did anybody so far create an action which creates a dependency graph of the connected assets?

    We started tracking every version in Ftrack and link the versions between them.

    Sometimes we can reach more than 10 layers.

    It's nice that we can view the links in Ftrack, but adding them in a graph would look nicer.