-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Spreadsheet ApiComment getTime always return zero #2753
Comments
@EdwardCheck Thank you for your issue. I have registered a bug |
It would be more correct to have this issue on the DocumentServer project. For this reason, it will be rescheduled |
Thanks for your reply, I would like to know if the next version will be fixed? I'm using Document Builder v8.0.0.99 |
Yes, I will inform you after the fix is released |
This issue is unique.
Operating System
Windows 10 / 8.1 / 7
Version information
8.0.0.99
Expected Behavior
When I get spreadsheet comment api getTime, I want it return create timestamp
Actual Behavior
Use Spreadsheet API -- ApiComment -- getTime , it always get zero. The same api in Document worked. See Under Steps, it looks wrong on your doc website.
Reproduction Steps
https://api.onlyoffice.com/docbuilder/spreadsheetapi/apicomment/gettime
![image](https://private-user-images.githubusercontent.com/25213289/336802697-59c02882-f6f6-4404-8f46-c7c7ec344b21.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM5NjI1ODYsIm5iZiI6MTcyMzk2MjI4NiwicGF0aCI6Ii8yNTIxMzI4OS8zMzY4MDI2OTctNTljMDI4ODItZjZmNi00NDA0LThmNDYtYzdjN2VjMzQ0YjIxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDA2MjQ0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRmYzY5MTE4Zjg5YmQyODIyNDRjOGUxMzJlNWI5NDljMGRjN2I0YzQxOGE1NzI1OTJlZTYyYWZmM2I0M2VlOGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.GV8z6o0lPOnRL6bpB_UVLFUR1c5nPE6Y2AzLLAVWj2M)
Additional information
No response
The text was updated successfully, but these errors were encountered: