Are the table names for GP 10 the exact same as GP 9?
And the answer is: for the most part, yes. Here is the master table reference.
There is a pretty good table reference here:
http://dyndeveloper.com/dynModule.aspx
Also, if you have access to customersource with Microsoft Dynamics GP you can also download the SDK which will give you all the version changes, along with entity relationship maps that you can use as well for troubleshooting any db issues.
Related
I'm using QuestDB and SQL for the first time, and I stumbled upon the LATEST_ON syntax used in QuestDB. Can someone explain it's usage and where to use it?
Quoted from the docs:
For scenarios where multiple time series are stored in the same table, it is relatively difficult to identify the latest items of these time series with standard SQL syntax. QuestDB introduces LATEST ON clause for a SELECT statement to remove boilerplate clutter and splice the table with relative ease.
For more information visit the official documentation
LATEST ON is to find the latest record for each unique time series in a table. See this page for some examples: https://questdb.io/docs/reference/sql/latest-on/
It gives you the latest available record for each combination of the PARTITION BY values, according to the ON timestamp
Maybe easier to understand with an example. If you go to https://demo.questdb.io you can execute this query
select * from trades latest on timestamp
partition by symbol, side
It will then show you the latest existing row for each combination of Symbol and Side. If you wanted to do this using standard SQL, you would probably have to use a window function, something like this
select * from
(select *
,ROW_NUMBER() over (partition by Symbol, Side
order by timestamp DESC) AS RowNumber
from trades where timestamp > '2022-10-01') t
where t.RowNumber = 0
Latest on retrieves the latest entry by timestamp for a given key or combination of keys, for scenarios where multiple time series are stored in the same table.
Check this link for some examples: https://questdb.io/docs/reference/sql/latest-on/
I have a problem with Bing Map on Power BI.
In my database I have a Place called Ribeirão Gonçalves, Piauí, Brasil (City, State, Country).
I can see on the bing map website that this place does not exist on the map, and in Power BI It shows me some random area in the State Piauí, Brasil.
Also the same problem I have with Place called Terezópolis de Goiás, Goiás, Brasil, but this time the city can be found on the Bing map on the Internet but still shows wrong area.
My question is how to prevent this kind of situations? Does anyone have experience resolving such scenarios using Bing maps?
Thanks in advance
Turns out, The problem is with Bing maps, where information about places are incorrect. The problem will be solved by Bing Support Team. It will take few months. If someone has similar issue it is good to inform them.
Is there any hint or directive that can be used with EXPLAIN of a query on Azure SQL Data Warehouse that would return recommended statistics that were not available for the optimizer? Alternatively is there a tool that can analyze a workload and make any recommendation.
Today, no. Right now the recommendation is to create statistics on every column as these are needed to create an optimal parallel query plan (I.e. how to move data around between nodes to return a result since it's a MPP architecture).
https://learn.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-best-practices#maintain-statistics
An example of how to script this out can be found here as well (example H).
https://learn.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-tables-statistics#examples-create-statistics
As you know, statistics should be created (according to this article):
on columns involved in JOINs, GROUP BY, HAVING and WHERE clauses.
There are no tools to do this (yet), but if you have access to the EXPLAIN plans they give you certain information. For example the shuffle_columns element lists all columns involved in a SHUFFLE_MOVE:
<shuffle_columns>col;</shuffle_columns>
as well as myriad other information. Review the annotation I did of an Azure SQL Data Warehouse plan here.
Lastly, (and I haven't actually done this, I've only been thinking about doing it), you could set up a copy of your database on SQL Server 2016, bearing in mind the syntax differences (eg distribution, lack of unique indexes etc). this would give you access to certain useful resources like execution plans, including index suggestions, and certain trace flags which tell you what stats were used. I mean the database engines and indexing are really different so I don't know how worthwhile this might be. I'll post back if I progress my thinking on this. I do find the question "Why is this query going slow?" much harder to answer on this platform that ordinary "box product" SQL Server because the tools aren't as mature yet.
I am new to PowerBI and I am trying to get data from Dynamics Nav 2016 in PowerBI Online and I get this error:
We couldn't import data from Microsoft Dynamics NAV
Make sure you're entering the information correctly.
Please try again later or contact support. If you contact support, please provide these details.
Data source type
Processing errorThe column 'No' of the table wasn't found.
Correlation ID28883962-32de-95fe-bf97-85f2c3699964
Activity ID558a71dd-3cee-455e-a8e7-6b00180688f6
Request IDe864480c-e56e-287f-d891-f21a816076ff
Status code500
TimeMon Oct 31 2016 17:09:44 GMT+0200 (GTB Standard Time)
Version13.0.1700.493
Cluster URIhttps://wabi-north-europe-redirect.analysis.windows.net
Has anybody encountered something similar?
Make sure all oData feeds have data in them.
In my example of this issue, I had to create a Opportunity so that the "SalesOpportunities" feed had at least one entry in it. Otherwise, it caused the error you noted above.
This also means making sure your Account Schedule KPIs has values too.
I wouldn't view the Content Pack as anymore than Demo-esque material. 9 times out of 10 it's not tailored to the organization so the graphs aren't as useful.
I am trying to increase a field number whenever a new row is added to my table. First I created a variable lastItem specified as a Record with Subtype to my Table. Now I created the following Code on the OnInsert() trigger:
lastItem.FINDLAST;
ItemNo := lastItem.ItemNo + 10;
The above code seems not to work on the OnInsert() trigger but works for one row when I enter it on the ItemNo - OnValidate() trigger.
Any ideas how to get an increasing Number on every new row in my table?
Are you sure that's Dynamics CRM? The code is a Dynamics NAV C/AL code and you talking about the Item table? In this case let NAV to give you the next number from the No. Series properly.
You can use the same approach in any other table : related pattern
You should stay away from doing direct SQL updates and adding triggers to the DB when using Dynamics CRM as it's not supported.
The appropriate way would be to use a plug-in which reads the last value and then does the increment. You'd would register this to run when a new record is created in the system.
You can find some example source code on this CodePlex project: CRM 2011 Autonumbering Solution
You should use the property autoincrement of the field. In this way you increment the field one on one in every row.