Known Issues
Urgent
The Update Billing History wizard can assign billing history to the wrong portfolio under certain data conditions.
- There are no transactions entered for the portfolio.
- A Billing Spec has been assigned to the portfolio.
- The portfolio is included in the Update Billing History job, either because it is selected, it is included in the selected Set, or the job is run on All Portfolios.
- Instead of running the Update Billing History wizard, create a batch printing job that includes the Billing Statement. Run the batch printing job, choosing to export to a single PDF. This is the easiest option to implement.
- Remove the Billing Specification from any portfolio that has no transactions entered.
- Run the Update Billing History wizard only on a Set, and include in the set only portfolios that have transactions entered.
- In any portfolios that have no transaction history, create a Journal transaction for the amount of $0 prior to running the Update Billing History wizard.
Important
This release is incompatible with Junxure’s Junxure.SPTExporter.exe.
IDC price downloads may be copying stale pricing data following upgrade to version 5.10
(1818)
Issue with same-day flows when excluding flows and billing by category
(38998)
A page with a PVCNI (Portfolio Value versus Cumulative Net Investment) chart does not generate a report.
(168661, 169186, 178235)
Change the Date Range setting for the PVCNI graph to a shorter date range.
Increase the horizontal space available for the graph by adjusting the left and right page margins.
Switch from a pre-defined page to a user defined page (i.e., from the Portfolio Overview page to the Portfolio Overview Sample page).
Accrued interest on a CD incorrect in some cases on statement reports
(25638)
Cash Invested 1 is sometimes incorrect when a position is completely closed and re-opened on the same day
(32968)
De Minimus rule for amortizations uses the receipt/credit date instead of Original Trade Date
The De Minimus rule is:
If the discount is less than ( redemption value * 0.25% * number of years until redemption ), then do not create transactions.
For bonds entered using a Receipt or Credit transaction, instead of the Original Trade Date, PortfolioCenter uses the Receipt or Credit Date, and the cost basis at the time of the Receipt or Credit to determine whether to generat amortizations or not. This can result in amortizations being generated for bonds when they should be not.
(127833)
Dividends on short positions appear as positive rather than negative amounts on performance reports.
Peformance Returns (TWR and IRR) and Investment Gain are not affected by this issue. However, the Income component of the portfolio is overstated, and the Unrealized Gain is understated by twice the amount of the dividend.
(32782)
Error message - "Property [field name] not found" when you run a View.
This issue occurs when:
- A Custom Field has been added to a View as a column.
- The name of the Custom Field has been changed after it was added to the View.
The next time the view is run, the View still expects the old Custom Field name to exist. The error message is produced: "Property [field name] not found," where [field name] is the old name of the Custom Field.
(30469)
- Choose "Continue" when the error is produced.
- Edit the View (Right-click on the View and choose "Edit").
- Choose the Columns tab.
- The old Custom Field name will appear in the list of selected columns. Remove it.
- Find the new Custom Field name in the list of available columns. Add it to the selected columns.
- Choose OK and run the View.
Factor information is being overwritten by interface posting
(26394)
In PortfolioCenter, the program can be set to read factors from past dates. To enable this setting, go to:
Securities Tab | Tools |Modify Security Type Settings | Mortgage-Backed.
Change the setting labeled Factors Valid For to 32. This setting allows you to post factors once a month, generally when they change.
The Asset Class Performance summary report on a group displays the target from an underlying account.
(26236)
Trading data export fails with a 'remote procedure call' error
When running the Trading data export with one or more of the Realized Gain/Loss sections selected, the export fails with the following error:
Error: The remote procedure call failed.
System.Runtime.InteropServices.COMException (0x800706BE):
The remote procedure call failed.
at SchwabPT.PortfolioMgmt.DataExport.Trading.TradingBlobExportPlugin.
OnExecute()
at SchwabPT.PortfolioMgmt.DataExport.Extensibility.ExportPlugin.SchwabPT.
PortfolioMgmt.DataExport.Extensibility.IExportPlugin.
Execute(ExportFormat format)
at SchwabPT.PortfolioMgmt.DataExport.Extensibility.Export.DoExecute()
(27019)
(27019)Use of the new Data Set Copy will fail where a portfolio has no transactions.
The user can not pick a Category Color Name using the mouse when using a remote connection.
The Billing Account Number does not appear on the Client Presentations Billing Page
In Client Presentations, the Billing Account is not displayed under the following conditions:
Running the Billing Statement for an individual Portfolio, or for a Group while choosing not to Allocate Bill to Group Members
The setting "Display Billing Account Number" is set to True.
(TFS 146238)
Fonts for numbers in specific sections of presentations are replaced with Microsoft Sans Serif font during batch printing.
(148680)
A page with a PVCNI (Portfolio Value versus Cumulative Net Investment) chart appears off-center in batch mode
When running a Batch Job that includes overview pages with a PVCNI graph, if the PVCNI graph exceeds a certain number of periods (the exact number of periods varies depending on the space available for the graph; typically it is between 15 and 18 periods), the overview pages for that particular portfolio or group will be off centered to the upper left. This does not happen if the presentation is run individually (i.e. from the Reports | Client Presentations screen).
(148106)
If only a few portfolios are affected, run the presentation individually for those portfolios.
Change the Reporting Frequency setting for the PVCNI graph to Annual.
Batch Printing issue on Windows Server 2012
(164483)
Index Standard Deviation Column on Composite Reports Generates Incorrect Results for Targets
(40077)
Missing Data Point in the Trading Data Export
For assistance please contact Technical Support at 800-528-9595, option 4.
Note: If you produce the Trading Data Export for use with any third-party software platform, do not make any additional changes to the file format without first validating the changes with the third-party software provider.
Fixed income securities that mature may create two transactions instead of one sell transaction
(252056)
Cash merger transactions may create two transactions instead of one sell transaction
(255056)
FYI
"Command Failed" when processing Batch updates for Smart Sets simultaneously in different datasets.
(29441)
Global Performance Review: Inconsistent display of accounts with no performance
The Global Performance Review is inconsistent in handling the display of accounts with no performance intervals for any of the requested reporting periods.
Some accounts display two dots (..) in the spaces provided for the returns, other accounts are not included on the report at all.
In Centerpiece, all accounts that do not have intervals for the requested time periods are included on the report, but with two dots in all of the return columns.
(24470)
In the Columns tab of the Edit View dialog - "An item with the same key has already been added."
(168661, 169186, 178235)
Change the Date Range setting for the PVCNI graph to a shorter date range.
Increase the horizontal space available for the graph by adjusting the left and right page margins.
Switch from a pre-defined page to a user defined page (i.e., from the Portfolio Overview page to the Portfolio Overview Sample page).
Purchase of multiple lots of one CD can cause mismatch between Interval values and holding reports
(39425)
"Portfolio Description" field behavior changed in Portfolio Data Manager
(39699)
Trust File Build Files are not deleted with the delete date range function
(186663)