I agree, this functionality has opportunity for alot of improvements. Why can't this connect to the budget and show all accounts with department dimensions. How does everyone else grab the net change in the period for this data in order to create real time operational reports for actuals to budget variance? We built a report in BI but it is not real time. Shouldn't there be a real time standard report in BC to do this?


When the built-in Scanpst.exe tool fails to repair a corrupted OST file, Shoviv OST to PST Converter emerges as a reliable alternative to restore your valuable Outlook data. Here's a step-by-step guide on how to open your OST file using Shoviv OST to PST Converter:


  1. Download and install Shoviv OST to PST Converter on your computer.
  2. Ensure that Microsoft Outlook is closed during the conversion process.


1. Launch Shoviv OST to PST Converter:

  • Open the Shoviv OST to PST Converter application.

2. Select the OST File:

  • Click on the "Add" button to browse and select the corrupted OST file you want to repair.

3. Choose the Conversion Mode:

  • Select the desired conversion mode:
  • Standard Mode: Suitable for most OST files with minor corruption.
  • Advanced Mode: Handles severely corrupted OST files.

4. Specify the Destination Folder:

  • Click on the "Browse" button to choose the location where you want to save the converted PST file.

5. Initiate the Conversion Process:

  • Click on the "Convert" button to start the conversion process. Shoviv OST to PST Converter will scan, repair, and convert the selected OST file to PST format.

6. Open Converted PST File in Outlook:

  • Once the conversion is complete, launch Microsoft Outlook.
  • Click on the "File" tab and select "Open".
  • Choose the converted PST file you just created and click "Open".

Your Outlook data should now be accessible from the converted PST file. Shoviv OST to PST Converter effectively repairs and converts corrupted OST files, ensuring that your valuable email data remains accessible and protected.


Additionally we had the following requirment some time ago

a list of Interfaces

Currently we often use codeunits as complex (dynamic type).

And it would be really helpful if I could specify the following:

ComplexList: List of [Interface "PTE Interface"]

See also there: https://github.com/microsoft/BCApps/issues/298#issuecomment-1824030146


This would be very useful and I don't see why it's not already possible if AP, AR and GL have this option.


Another related idea link to resolve issues within Advance bank reconciliations.



Microsoft product team must fix the FCR situation report to show incorrect exchange rate when doing cancelled/revered FCR.


The LCS link here: https://fix.lcs.dynamics.com/Issue/Details/?bugId=864682&dbType=3


Totally agree that this would be a huge benefit to be able to access generated reports quicker than thru the User interface. Our users have approximately 25 reports to include in a monthly reporting package and it takes about 1 minute per report to print to PDF--very inefficient use of time.


Not having all attachments flow to the posted invoice is non-intuitive to the user and not only leads to more time tracking down where the attachment is located, but can also result in a loss of documents if a partially invoiced PO/SO is deleted.

I believe this is a major flaw within BC since it creates scenarios where many documents can be unintentionally deleted without an organization even aware of this 'hole' within the BC attachment process.


We definitely need this improvement. All attachments should flow to the invoice even on partial receipts. This should also occur on the sales side as well!

We store all relevant external documents directly in BC. It has caused a bit of confusion within our company on partially invoiced documents on where to look for the attachment. Most folks expect it to be on the invoice, but all attachments except the last attached are still on the PO/SO. Not to mention that if a partially invoiced document (SO or PO) is deleted, the attachments are also deleted. The way this works is very unexpected and folks may end up losing documents because of it.


  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500