Bug 134211 - Incorrect function name in the document of PV
Summary: Incorrect function name in the document of PV
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-21 23:49 UTC by Hong Xu
Modified: 2021-06-11 03:50 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hong Xu 2020-06-21 23:49:16 UTC
The document of PV shows an incorrect function name. The syntax line shows the function name as Pmt, but it should be PV. The example at the bottom of that page uses the correct function name.
Comment 1 Xisco Faulí 2020-07-13 14:43:13 UTC
What is the document of PV ?
Comment 2 sdc.blanco 2020-11-11 14:19:03 UTC
@Mike -- can you help here.

I believe this bug report is about the PV function in Calc.

Here is Syntax (both in Function Wizard and relevant webpage) from:  https://help.libreoffice.org/7.0/en-US/text/scalc/01/04060103.html#pv

Syntax

PV(Rate; NPer; Pmt [; FV [; Type]])
Rate defines the interest rate per period.
NPer is the total number of periods (payment period).
Pmt is the regular payment made per period.
FV (optional) defines the future value remaining after the final installment has been made.
Type (optional) denotes due date for payments. Type = 1 means due at the beginning of a period and Type = 0 (default) means due at the end of the period.

As I understand OP, Pmt is supposed to be wrong.

I also looked at the PMT function: 
https://help.libreoffice.org/7.0/en-US/text/scalc/01/04060119.html#pmt

If you cannot see anything wrong with those functions, then maybe this should be closed as INVALID or NOTABUG ?

cc: Mike Kaganski
Comment 3 Mike Kaganski 2020-11-11 14:22:59 UTC
(In reply to sdc.blanco from comment #2)

I believe that OP should first answer the question in comment 1. Because it's quite possible that the problem is e.g. in some guide, or maybe in some translation.
Comment 4 QA Administrators 2021-05-11 03:51:49 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-06-11 03:50:31 UTC
Dear Hong Xu,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp