Skip to content

[BUG] Update Page does not support Status type #6310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jasueh opened this issue May 5, 2023 · 5 comments · May be fixed by #6372
Closed

[BUG] Update Page does not support Status type #6310

jasueh opened this issue May 5, 2023 · 5 comments · May be fixed by #6372
Assignees
Labels
blocked Issue is blocked pending a resolution bug Something isn't working prioritized Prioritized issue triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@jasueh
Copy link

jasueh commented May 5, 2023

Describe the bug
When updating a page, status type properties are not updated.

To Reproduce
Steps to reproduce the behavior:

  1. Retrieve Page from Notion, page in database must include at least 2 properties Status of type status and Updated type Text . Status should be anything but In Progress
  2. Update Page component, set id with the retrieved page
  3. Set Properties Types: ["Status", "Updated"]
  4. Set Properties Values: [ {
    "id": "abcc967b-5135-4217-8677-ba840fd8b008",
    "name": "In progress",
    "color": "blue"
    }, "Done"]
  5. Test it

Expected behavior
The page should have the Status and Updated fields updated with the values mentioned in the steps to reproduce.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Chrome
  • Version: Version 113.0.5672.63 (Official Build) (64-bit)

Additional context
From what I understand, the Status type is an object with 3 properties as per notion documentation: https://developers.notion.com/reference/page-property-values#status

reviewing the source code of the update_page component, led me to the notion page properties common resource:
https://github.com/PipedreamHQ/pipedream/blob/master/components/notion/common/notion-page-properties.mjs

And it seems that status is not included in the integration.

@jasueh jasueh added the bug Something isn't working label May 5, 2023
@vunguyenhung vunguyenhung added the prioritized Prioritized issue label May 8, 2023
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label May 8, 2023
@lcaresia lcaresia self-assigned this May 9, 2023
@lcaresia lcaresia linked a pull request May 9, 2023 that will close this issue
@lcaresia lcaresia added the blocked Issue is blocked pending a resolution label May 15, 2023
@lcaresia
Copy link
Collaborator

Isn't possible to update stats type field by API, only from Notion UI.
One solution is change the Status field to type select

image

https://developers.notion.com/reference/property-object#status

@jasueh
Copy link
Author

jasueh commented May 15, 2023 via email

@lcaresia
Copy link
Collaborator

@dannyroosevelt Can I delete this task?

@dannyroosevelt dannyroosevelt closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
@dharrison4
Copy link

dharrison4 commented Jul 3, 2023

Hello @lcaresia , I think this issue was closed because the API limitation text was misunderstood.

The API warning text is specifically telling you what its limitations are:

  • You cannot change the Status name label, (1) 'Project Phase' in my example.
  • You cannot change the Status options directly, (2) 'do NOW' or 'Meh' in my example. You cannot, say, create a new Status option for "Delegated", or rename "do NOW"→"DO IMMEDIATELY"

What you can do, which is not specifically outlined in the warning:

  • You can select what the (2) Status is from the list of options that already exist, 'Meh' in our example below.

image

Could somebody please consider reopening this and taking another look, please?

@lcaresia
Copy link
Collaborator

lcaresia commented Jul 5, 2023

@dharrison27 I will take a look on this, thanks for your research about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Issue is blocked pending a resolution bug Something isn't working prioritized Prioritized issue triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants