You not meant to mark you answer as verified XD. Anyway approach with VIEW_TABLE_USAGE is not the best one because one data entity could use another data entity as a data source or it can use a view, in this case only traversing tree of crossreferences can help you.
↧
RE: Cross reference between AX tables/columns and DIXF Data Entities? (Migrating ETL from reading AX tables directly to Data Entities)
↧
RE: Cross reference between AX tables/columns and DIXF Data Entities? (Migrating ETL from reading AX tables directly to Data Entities)
Oh, sorry about that, I'm used to sites like stackoverflow where the point is for people to find answers to questions. If you want to make another post containing the answer I'd be happy to mark that as the accepted answer.
> VIEW_TABLE_USAGE is not the best one because one data entity could use another data entity as a data source or it can use a view, in this case only traversing tree of crossreferences can help you
Hmmmmmm. Is there a better approach one could use, that is *not* subject to these same downsides? A useful rule of thumb that works most of the time is more useful than "it depends", at least to someone like me who lacks deep experience on AX. The VIEW_TABLE_USAGE approach seems like it could be useful to those of us with lesser experience much or perhaps even most of the time.
↧
↧
RE: Payment by ACH
Vendor bank account has to be added to the payment tab on the vendor after setting up the vendor bank info.
↧
RE: Cross reference between AX tables/columns and DIXF Data Entities? (Migrating ETL from reading AX tables directly to Data Entities)
So VIEW_TABLE_USAGE will work in most cases, but, for example, if data entity works with addresses it always uses address data entity instead of table, so this approach wont work for them.
You have DYNAMICSXREFDB data base on your VM that is populated during crossreferences build. It has only 5 tables, so should not be too hard to figure out how to use them. You can build a tree like PurchLine -> PurchLineSomethingView -> PurchLineSomethingDataEntity.
Talking about answers you can click on any that helped you and mark it as verified.
↧
RE: Cross reference between AX tables/columns and DIXF Data Entities? (Migrating ETL from reading AX tables directly to Data Entities)
I'm not seeing how any table in DYNAMICSXREFDB provides insight into this problem, is there something I'm overlooking?
> Talking about answers you can click on any that helped you and mark it as verified.
Oh, whenever reading these forums, I've always thought that the answer that is marked "Verified Answer" is the one that is the correct answer (or in this case, the "most correct possible"), is it actually moreso a way of awarding points, but the reader has to figure out on his own what the correct answer is? Is there a "how to use these forums" document I should have read before asking questions?
EDIT: Ok, I see what you mean now with entities based on entities:
select * from INFORMATION_SCHEMA.VIEW_TABLE_USAGE where view_name like '%address%ENTITY'
That yields several results where TABLE_NAME references some %ENTITY objects, an outer join to sys.objects returning type_desc would make that scenario fairly obvious, but it's still in a useful direction, it's just not final.
However, for this specialized scenario, where you are starting with a table name and working towards a Data Entity, because you're *starting* with a table (from a pre-existing ETL project in this case).
It would be so nice if some of these things were documented somewhere, it feels like some sort of a party game where you're solving a mystery.
↧
↧
RE: Payment by ACH
Can you send me a screenshot please to make sure about it?
↧
RE: Payment by ACH
Please check above. Select the account which you created In vendor bank account
↧
Payment by ACH
Hi,
I am trying to pay a vendor by ACH. I am getting the message 'A bank account has not been set up for the vendor'. I have defined the routing number and bank account # in the vendor> Vendor bank accounts, as well I made sure that in the payment journal , bank tab, I specified the 'account identification field'. What else can be missing?
Thanks
↧
RE: Cross reference between AX tables/columns and DIXF Data Entities? (Migrating ETL from reading AX tables directly to Data Entities)
Look at [References] it has sourceId, targetId and kind. [Names] links Id to a path. So for purch line you can find id by using next select:
SELECT * FROM [DYNAMICSXREFDB].[dbo].[Names] a where a.path like '%purchLine'
Kind is an enum
public enum CrossReferenceKind
{
/// <summary>
/// Type not specified. Used for queries
/// </summary>
Any = 0,
/// <summary>
/// Indicates that the reference is a Method Call
/// </summary>
MethodCall = 1,
/// <summary>
/// Type reference
/// Indicated that the type is used (variable and field declaration, attributes, function return type, etc)
/// </summary>
TypeReference = 2,
/// <summary>
/// Interface implementation
/// Indicates that the source entity is implementing this interface
/// </summary>
InterfaceImplementation = 3,
/// <summary>
/// Class Extended
/// Indicates that the source entity is extending this class or interface
/// </summary>
ClassExtended = 4,
/// <summary>
/// Test Call
/// Indicates that the source entity (test) directly or indirectly calls an application method.
/// </summary>
TestCall = 5,
/// <summary>
/// Property
/// Indicates that the source entity has a certain property.
/// </summary>
Property = 6,
/// <summary>
/// Attribute reference
/// Indicated that an Attribute is used
/// </summary>
Attribute = 7,
/// <summary>
/// Test Helper Call
/// Indicates that the source entity is a test helper.
/// </summary>
TestHelperCall = 8,
/// <summary>
/// Metadata or code Tag reference
/// Indicates that the source tag is used on a metadata element, class or a method or a line of code.
/// </summary>
Tag = 9,
}↧
↧
RE: difference between drill down and drill through
Drill through AX 2012:
A drill-though is a hyperlink embedded directly in the report content. These hyperlinks can be statically defined in the report definition or generated dynamically based on the reporting session context including user security rights, AX metadata, and configuration keys.
Supported URL targets:
Forms in the AX rich client
Enterprise Portal pages
Internet/intranet sites
SSRS reports
Drill down AX 2012:
Drill down or up actions allow users to drill into the data that is of most interest to them by expanding and collapsing sections of data within a report
↧
difference between drill down and drill through
Dear All,
Can you please let me know what is the difference between drill down and drill through in SSRS report ?
Can we use both (drill down and drill through) at same report ?
Please give me more shed on this.
Thanks!
Arpan
↧
RE: AX Retail - D365 Distribution Schedule Jobs - Not Working
Any further updates on it?
Thanks,
Riz
↧
AX Retail - D365 Distribution Schedule Jobs - Not Working
Hi All,
im new to D365 AX retail , while running any of the distribution schedule jobs it is taking lot of time
for ex: i have run staff job ( 1060 ) it is taking lot of time ,after that below is the error message system flashed
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: id
at Microsoft.DynamicsOnline.Infrastructure.Components.SharedServiceUnitStorage.SharedServiceUnitStorage.DeleteData(String id, String category)
at Dynamics.AX.Application.RetailCDXPackageStore.deletePackage(Int64 dataGroupRecId, RetailCDXDownloadUpload direction, String fileIdOrFullPath) in xppSource://Source/Foundation\AxClass_RetailCDXPackageStore.xpp:line 79
at Dynamics.AX.Application.RetailCDXDataSync.deleteDataFile() in xppSource://Source/Foundation\AxClass_RetailCDXDataSync.xpp:line 259
--- End of inner exception stack trace ---
Regards,
Naresh
↧
↧
RE: What is the difference between Customer requisition and Customer reference fields?
Where can i setup a customer reference and distributor PO number? Cant find any information or tutorials about this topic that works.
↧
What is the difference between Customer requisition and Customer reference fields?
Newer to AX. Going live soon. What is the difference between the Customer requisition and Customer reference fields? I noticed that the field names are (SalesTable).PurchOrderFormNum and (SalesTable).CustomerRef, respectively.
Does the system use one field differently than the other? It seems like they were meaning for the Customer Requisition field to be PO field due to the name of the field?
↧
RE: Dynamics AX menu not available in Visual Studio
VS2013 is not going to help , you need VS 2015 . As per requirement development requires VS 2015 Professional for standard development activities. However, if you want to develop and run performance and load tests, you will need VS 2015 Enterprise.
community.dynamics.com/.../the-new-dynamics-ax-and-visual-studio-licenses
↧
Dynamics AX menu not available in Visual Studio
I have D365 for Operation is available on Cloud with Application URL and User Credentials . I installed VS2013 to do Customizations but Dynamics AX menu item do not available in Visual Studio
↧
↧
RE: update_recordset not considering where condition for temp tables
What is dimNameTmpDesc in setting clause ? I don't see that table used In your while select,that could be the issue
↧
RE: update_recordset not considering where condition for temp tables
Jay and Sukrut,
Sorry, i corrected the question. there are only 2 temp tables. It was typo.
_ledgerTrialBalanceTmp and _dimensionFocusNameTmp
I am facing this problem while using these 2 temp tables..
Kindly let me know if you've faced this before.
↧
update_recordset not considering where condition for temp tables
Hello,
I have 2 temp tables which gets created in tempdb of the sql server.
I am updating as shown below in D365
ttsbegin;
update_recordset _ledgerTrialBalanceTmp setting
DCCDimensionName1 = _dimensionFocusNameTmp.DimName1,
DCCDimensionName2 = _dimensionFocusNameTmp.DimName2,
join _dimensionFocusNameTmp
where _dimensionFocusNameTmp.LedgerDimension == _ledgerTrialBalanceTmp.LedgerDimension;
ttscommit;
Now when this gets executed, i could see in SQL Profiler that it's eliminating where condition and hence values gets wrongly updated.
Surprisingly, update using while select statement works fine.
while select forupdate _ledgerTrialBalanceTmp
{
select _dimensionFocusNameTmpwhere _dimensionFocusNameTmp.LedgerDimension== _ledgerTrialBalanceTmp.LedgerDimension;
_ledgerTrialBalanceTmp.DCCDimensionName1 = _dimensionFocusNameTmp.DimName1;
_ledgerTrialBalanceTmp.DCCDimensionName2 = _dimensionFocusNameTmp.DimName2;
_ledgerTrialBalanceTmp.update();
}
What is the issue with this update_recordset statement?
↧