Thursday, March 26, 2020
Wednesday, March 25, 2020
Devops - Future iterations aren't showing in the Delivery Plans function
- Cause
- You used the Project Configuration to define new sprints, but did not actually create new sprints in the Backlog
- Resolution
- From Backlogs>Planning Create new sprints
- It will use the predefined sprints from the project configuration if they were defined
- Otherwise, you can define new sprints
- These will now display in the delivery plan
Dynamics NAV / Business Central - Payment Application View
SELECT INV.timestamp, INV.[Entry No_], INV.[Vendor Ledger Entry No_], INV.[Entry Type] AS InvType, INV.[Posting Date], INV.[Document Type], INV.[Document No_], INV.Amount, INV.[Amount (LCY)], INV.[Vendor No_],
INV.[Transaction No_], INV.[Debit Amount], INV.[Credit Amount], INV.[Debit Amount (LCY)], INV.[Credit Amount (LCY)], INV.[Applied Vend_ Ledger Entry No_], INV.Unapplied, INV.[Unapplied by Entry No_],
INV.[Application No_], PAY.[Entry Type] AS PayType, VLEPAY.[Document Date] AS PaymentDate, VLEPAY.[External Document No_] AS PayExtDoc, VLEINV.[Document No_] AS INVDocNo,
VLEINV.[Document Date] AS INVDocDate, VLEINV.[External Document No_] AS INVExtDoc
FROM dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS INV INNER JOIN
dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS PAY ON INV.[Vendor Ledger Entry No_] = PAY.[Vendor Ledger Entry No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEPAY ON PAY.[Document No_] = VLEPAY.[Document No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEINV ON INV.[Vendor Ledger Entry No_] = VLEINV.[Entry No_]
WHERE (INV.[Entry Type] IN (2, 4)) AND (PAY.[Entry Type] = 1) AND (INV.[Debit Amount] > 0)
INV.[Transaction No_], INV.[Debit Amount], INV.[Credit Amount], INV.[Debit Amount (LCY)], INV.[Credit Amount (LCY)], INV.[Applied Vend_ Ledger Entry No_], INV.Unapplied, INV.[Unapplied by Entry No_],
INV.[Application No_], PAY.[Entry Type] AS PayType, VLEPAY.[Document Date] AS PaymentDate, VLEPAY.[External Document No_] AS PayExtDoc, VLEINV.[Document No_] AS INVDocNo,
VLEINV.[Document Date] AS INVDocDate, VLEINV.[External Document No_] AS INVExtDoc
FROM dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS INV INNER JOIN
dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS PAY ON INV.[Vendor Ledger Entry No_] = PAY.[Vendor Ledger Entry No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEPAY ON PAY.[Document No_] = VLEPAY.[Document No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEINV ON INV.[Vendor Ledger Entry No_] = VLEINV.[Entry No_]
WHERE (INV.[Entry Type] IN (2, 4)) AND (PAY.[Entry Type] = 1) AND (INV.[Debit Amount] > 0)
Monday, March 23, 2020
Dynamics NAV, business Central - Web client - "Working On it" timeout error
Problem:
Solution:
- This happens on sales return order>get documents to reverse
Solution:
- Use a different Browser
- Chrome or Edge do not suffer from this issue.
- Explorer does.
Friday, March 13, 2020
Business Central - Demo Install, cannot login to web client - Add nav user
The user account you are currently using cannot login to Business Central.
Add another user account with super permission.
Error: You are not setup as a valid user
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2013r2/jj672890(v=nav.71)
If you are restoring from an external database, Add your windows account to the database using SSMS to ensure the powershell can even interact with the db.
Give it db_owner to the db and master
From powershell or administration shell, run as administrator
New-NAVServerUser MicrosoftDynamicsNavServer -WindowsAccount Cronus\Chris
New-NAVServerUserPermissionSet DynamicsNAV71 –WindowsAccount cronus\chris -PermissionSetId BASIC
New-NAVServerUserPermissionSet CRONUS –WindowsAccount cronus\Joe -PermissionSetId SUPER
eg.
New-NAVServerUser BC150 -WindowsAccount mypc\test New-NAVServerUserPermissionSet BC150 –WindowsAccount mypc\test -PermissionSetId SUPER
Add another user account with super permission.
Error: You are not setup as a valid user
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2013r2/jj672890(v=nav.71)
If you are restoring from an external database, Add your windows account to the database using SSMS to ensure the powershell can even interact with the db.
Give it db_owner to the db and master
From powershell or administration shell, run as administrator
New-NAVServerUser MicrosoftDynamicsNavServer -WindowsAccount Cronus\Chris
New-NAVServerUserPermissionSet DynamicsNAV71 –WindowsAccount cronus\chris -PermissionSetId BASIC
New-NAVServerUserPermissionSet CRONUS –WindowsAccount cronus\Joe -PermissionSetId SUPER
eg.
New-NAVServerUser BC150 -WindowsAccount mypc\test New-NAVServerUserPermissionSet BC150 –WindowsAccount mypc\test -PermissionSetId SUPER
Thursday, March 12, 2020
International Global Barcode, Category Database Lookup
GS1 and other
https://barcodesdatabase.org/barcode/5021265244164
GTIN
http://product-open-data.com/search
Global Product Categories
https://www.gs1.org/services/gpc-browser
https://barcodesdatabase.org/barcode/5021265244164
GTIN
http://product-open-data.com/search
Global Product Categories
https://www.gs1.org/services/gpc-browser
Wednesday, March 11, 2020
NAV / BC 14 - Intercompany Setup
Step 1: Copy/Create New
companies:
In order to
begin this setup, you need to either create a new company or in this case, copy
your current company as another.
·
Search
‘Companies’
·
Highlight
desired company you wish to copy and click ‘Copy’ in the Home ribbon.
o
Enter
your new company name e.g ‘Cronus Distribution’
o
Click
Ok
o
The
new company will now be created
Step 2: Setup Companies
for intercompany transactions
·
Go
to ‘Company Information’ and setup the Intercompany Partner Code, IC Inbox Type
·
IC Partner Code: This is the Code each company must have and must be unique, for example
Company CRONUS13X is given the IC Partner Code ‘CRONUSLX’ (in the LSCentral1304
vm)
·
IC Inbox Type:
Select Database. File Location allows for manual export/imports of intercompany
transactions. Database sends it directly to the other company, no exports
needed.
·
IC Inbox Details: Only required if File Location is selected.
·
Auto Send Transactions: Yes. If unchecked, this would allow the sending company to push the
transaction using the “Intercompany Outbox Transactions” and accepted on the
other company using “Intercompany Inbox Transactions”. This is avoided by
checking the box.
·
This
needs to be done for all companies.
Step 3: Setup Intercompany
Partners
·
Go
to ‘Intercompany Partners’
·
Click
New
·
Put
in the other company IC Partner Code in the Code field
·
Select
currency
·
Transfer type:
Database
·
Company Name:
Select company for this IC partner
·
Auto Accept Transactions: Check if you do not want to vet the documents in the Intercompany
Outbox/Inbox Transactions page and would like the transactions to integrate to
the other companies automatically.
·
Customer No: Select
a customer code for this IC Partner if necessary (You need to create a new IC
Partner Customer Card for this)
·
Select
Receivables Account
·
Outbound Sales Item No Type: Internal No.
·
Vendor No:
Select IC vendor and select Payables account.
·
Outbound Purch. Item No Type: Internal No.
Step 4: Setup Intercompany
Chart of Accounts
In order
for a group of companies to make intercompany transactions, they must agree on
a chart of accounts to use as a common reference.
·
Go
to ‘Intercompany Chart of Accounts’
·
Enter
each account on a line in the window
·
If
the intercompany chart of accounts will be identical or similar to your regular
chart of accounts, you can fill in the window automatically by choosing ‘Copy
from Chart of Accounts’ action. You can edit the new lines as needed.
Step 5: Ensure General
Posting Setups are correct
Based on
your Gen. Bus. Posting Group and Gen Prod. Posting Group selected
for your IC Customer/Vendor Card you need to ensure this is reflected in the
General Posting Setup of each company namely the Purchase Variance Account
and Direct Cost Applied columns.
Post Sales Orders:
·
Enter
the IC Customer No
·
Fill
in Sales order details
·
Before
posting you can go to Actions> Send IC Sales Order. This will send the order
as a Purchase Order to the desired IC Partner’s company.
·
When
opening the Purchase Order before posting in the partner company, fill in the
original sales order number of the sending company in the ‘Vendor Invoice No’
field.
Post Purchase Orders:
·
Enter
IC Vendor No
·
Fill
in Purchase Order details
·
Leave
the ‘Vendor Invoice No’ blank for now
·
Go
to Actions>Send Intercompany Purchase Orders
·
Switch
to the receiving company in BC and locate the Sales Order Number. Fill in the
Sales Order number in the Purchase Order ‘Vendor Invoice Invoice No’ in the
sending company.
·
You
can now post both transactions as needed on either company when the orders is
fulfilled.
Post IC General Journals:
·
Go
to ‘Intercompany General Journal’
·
Fill
in the fields as necessary
·
In
the ‘IC Partner G/L Acc. No.’ field enter the Intercompany General Ledger
Account that the amount will be posted into your partner’s company. This can be
setup as a default by going to the Chart of Account card for each company and
entering this field.
·
Click
Post
·
This
is now going to create a couple line entries in the other company. Switch to
the receiving company in Business Central and go to ‘Intercompany Inbox
Transactions’.
o
Select
the appropriate lines to send to the Intercompany General Journal Template
o
Select
‘Accept’ in Line Action column
o
Click
‘Complete Line Actions’ and a popup screen will then need to be filled in with:
o
IC Gen. Journal Template = INTERCOMP
o
Gen Journal Batch = DEFAULT
o
Starting Document No = This should default based on No series setup
o
You
can change the posting date if necessary by checking ‘Replace Posting Date’ and
entering the desired date
o
Filter
on where Line Action = Accepted.
o
Click
Ok
o
Your
journal lines in the receiving company is now transferred to the Intercompany
General Journal. You can now access there and post.
Tuesday, March 3, 2020
NAV NA - How to use regular Tax
- In General Ledger Setup, tick "VAT in Use"
- This will hide all tax fields, and enable all vat fields
Monday, March 2, 2020
NAV/BC 14.2 - Web Client - Control Column Layouts on Pages
- Page layouts are stored by profile role
- Run Nav in Configuration mode for the specific profile that needs to be adjusted
C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe -configure -profile:"Bookkeeper"
Microsoft.Dynamics.Nav.Client.exe -configure -profile:"Bookkeeper"
C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe -configure -profile:"Purchasing Agent"
Microsoft.Dynamics.Nav.Client.exe -configure -profile:"Purchasing Agent"
Microsoft.Dynamics.Nav.Client.exe -configure -profile:"Production Planner"
Subscribe to:
Posts (Atom)