Unabled to create Subscriptions with schedule as "On Extract Refresh"
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start with the SubscriptionItem class and the subscription serialization path described in the report. Determine how Tableau represents subscriptions triggered by extract refresh when no schedule_id is supplied, then verify that creation succeeds against the reported Tableau Server version without the None serialization error.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Subscriptions can be created on specific schedules. However, it is not possible to create subscriptions based on extract refresh. The SubscriptionItem class (subject, schedule_id, user_id, target) requires schedule_id as a mandatory parameter, so it cannot be ignored or set to None.
I have read some articles to ignore/ dont pass "schedule_id" but it doesn't seems to be working.
Env:
- Tableau Server: On Prem: 2025.1.1 (20251.25.0415.1018) 64-bit Windows
- Python version: 3.12.0
- TSC library version: 0.38.
To Reproduce
Try to create a subcription that should have schedule as "On Extract Refresh"
Results
Error When None is passed to Scheduled ID: new_sub = TSC.SubscriptionItem(email_subject, schedule_id=None, user_id, target)
INFO Creating a subscription (<Subscription subject(Test_User_TestSubscriptions2_withoutschedule) schedule_id(None) user_id(f57ca8cb-4a14-4b01-ac7b-721ffe260537) target(<Target#761209c1-decd-4626-8bbb-7be632e2efe8, view>))
Failed to create subscription. below is the error message
INFO cannot serialize None (type NoneType)
Error When Schedule_Id parameter is skipped: new_sub = TSC.SubscriptionItem(email_subject, user_id, target)
SubscriptionItem.init() missing 1 required positional argument: 'schedule_id'
please suggest if I'm missing any
- Lenguaje dominante
- Python
- Estrellas
- 716
- Forks
- 446
- Merge medio
- 8 d 8 h
- PR fusionados (30 d)
- 2
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de tableau/server-client-python
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
tableau/server-client-python#1865 ·
-
in-progress
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tableau/server-client-python#1829 · 1 comentario ·
-
enhancement gap needs investigation
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#1322 · 1 comentario ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule` Abiertohelp wanted Server-Side Enhancement ui-exists
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#1101 · 3 comentarios ·
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
tableau/server-client-python#783 · 5 comentarios ·
Todos los issues de tableau/server-client-python
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·