Best Of

Re: Business Central - Rolecenter Part Size

Hi,
I do not believe that you can control that (or is really meant to by Microsoft) but you can you it with Javascript addins, you can find some inspiration here:

https://www.youtube.com/watch?v=wEIEFwHUEkM&ab_channel=ErikHougaard

SanderDk

Re: Filetr On Closing DAte

in my system closing dates start with a "C"

so closing enteries for Dec 31, 2008 in are C123108

I can filter on that date and it works to show only closing entries.

now you can't use a wildcard and filter on C*

that gives an error of C* is not a valid date

one more thought, the source code for closing entries is CLSINCOME

so you can filter on that and see all closing enteries for any date.

themave

Re: Business Central 20.2 Application Upgrade to 20.10 fails (without performing a platform upgrade)

The System App under BC20.10 uses newer runtime, one that is not supported by BC20.2 platform.
If you want to upgrade apps to BC20.10, you will have to upgrade the platform as well, or make changes to the system and base apps and repackage as your own (not recommended!!!).

In fact, other than some select niche cases under old NAV, I have not heard of anybody wanting to upgrade apps, but not the platform

ShaiHulud

Re: the transaction cannot be completed because it will cause inconsistencies in the g/l entry table NAV

Very often this error happens when calculating Sales TAX, VAT GST etc. Often because of incorrect rounding, or sometimes because the last line is incorrectly rounded which is why it works the second time. Go into SQL and take a look at the actual decimal amounts un-rounded and see if there is a miss match.

David_Singleton

Re: Can't call CURRFORM.UPDATE from onValidate Code

Curr.Form.UPDATE - objective is to refresh data in controls - but in OnValidate trigger the system still does not know if the data which is validating are ok or not => system is not able to refresh data in the control...(you cannot update form within data processing trigger which is called in writing process)

It is clear? (it is only my explanation, I do not know exact or official reason...)

kine

Re: The runtime version '3.0' is not supported by the AL compiler

OK solved also this. Problem is in my app.json. Platform version must be: "13.0.0.0" not: "14.0.0.0",

weneed

Re: DataItemTableView, DataItemLink, OnPreDataItem - priority?

The answers an considerations are different for today's versions than back when that original question was posted. When upgrading a report, blindly following the original design can sometimes be the worse thing to do. Unfortunately, that is often what happens during an upgrade. Even Microsoft does it. They do seem to eventually get around to redesigning some reports

With older version, data was retrieved in pieces with each DataItem. Indented dataItems were retrieved for the related records only. Newer versions construct a compound SQL query to pull all the data at once.

Talking only about modern NAV\BC, the answer is it does not really matter. As they are all executed before the call to SQL is made. But the specifics can change the structure of the resulting SQL query and thus its performance.

bbrown

Re: Item Journal Posting with Tracking Spec.

OK, I've got this. Create Reservation Entry codeunit (99000830) is the key.
For example:

   ItemJournalLine.INIT;
   ItemJournalLine.VALIDATE("Posting Date",WORKDATE);
   .....
   ItemJournalLine.VALIDATE("Document Date",WORKDATE);

    CreateReservEntry.SetDates(
      0D, 0D);

    CreateReservEntry.CreateReservEntryFor(      
      DATABASE::"Item Journal Line",
      ItemJournalLine."Entry Type",
      ItemJournalLine."Journal Template Name",
      ItemJournalLine."Journal Batch Name",
      0,
      ItemJournalLine."Line No.",
      ItemJournalLine."Qty. per Unit of Measure",
      ItemJournalLine.Quantity,
      ItemJournalLine."Quantity (Base)",
      "Serial No.",
      '');

    CreateReservEntry.CreateEntry(
      ItemJournalLine."Item No.",
      ItemJournalLine."Variant Code",
      ItemJournalLine."Location Code",
      ItemJournalLine.Description,
      ItemJournalLine."Posting Date",
      ItemJournalLine."Document Date",
      0,
      3);
 
   ItemJnlPostLine.RUN(ItemJournalLine);

mr_ash

Re: How to create Item Tracking Lines automatically?

use codeunit 99000830. Here is a snippet of code that I used. All you would have to do is pass your own parameters and enter an applicable Lot No. for SomeLotNo. You can also do this for serial numbers.

CreateReservEntry.CreateReservEntryFor(
  DATABASE::"Sales Line",
  SalesLine."Document Type",
  SalesLine."Document No.",
  '',
  0,
  SalesLine."Line No.",
  SalesLine."Qty. per Unit of Measure",
  ABS(SalesLine.Quantity),
  SomeSerialNo,
  SomeLotNo);

CreateReservEntry.CreateEntry(
  SalesLine."No.",
  '',
  SalesLine."Location Code",
  SalesLine.Description,
  0D,
  SalesLine."Shipment Date",
  0,
  3);

canadian_bacon

Re: Issue in passing a String from NAV to a DotNet Method

@fazlehasan For any of the text variable in DotNet, you need to use something in DotNet only OR else system will keep prompting for the data type issue.

You may attempt using Variant if you wish to use the NAV one.

RockWithNAV