Hi, I’m not sure if this is the correct place to report a suspected bug, so please bear with me.
Current behavior: When creating a presentation link from folder on the website and then requesting the link via the API (Python request). The name value is set to None, instead of a string containing the name. If the presentation link is renamed, the name value will be set to a string containing the name.
Expected behavior: When creating a presentation link from folder on the website and then requesting the link via the API (Python request). The name value should be set to a string containing the name of the presentation link.
The way I’m requesting the presentation link is as follows:
import os
from frameioclient import FrameioClient
from dotenv import load_dotenv
load_dotenv()
client = FrameioClient(token=os.getenv("FRAME_IO_TOKEN"))
project_id = os.getenv("FRAME_IO_PROJECT_ID")
presentations = client._api_call("get", f"/projects/{project_id}/presentations")
The API call you’re making will just return the list of presentations, if you request the presentation individually, you will see that it is returned with the correct name.
At least, that’s what I saw when I tested this a few minutes ago. It’s possible we’re doing something weird in the list response, but a call to an individual presentation link via /v2/presentations/:presentation_id (f"/presentations/{presentation_id}" in the Python code) did work correctly for me.
I tested with requesting the presentation directly using it’s id. But the issue persists.
To reiterate. After creating a presentation from a folder, the name attribute is None. The name will only be present in the title attribute. If the presentation is made from a file or is renamed. The name attribute will be filled in.
Weird that this is happening for you, as it didn’t happen to me. When I created the presentation, both the name and title field were populated.
Is it possible that you’ve made more than one presentation for this particular folder? If that’s the case then I think I might know why it’s happening, but there will likely not be a solution coming.