Dear JonathanDries, Regarding your workaround (Our current workaround is to set the index uniqueness to false in the original table) , how do you apply this since all index properties are not editable in table extension?
↧
Forum Post: RE: Update table index using table extension
↧
Forum Post: RE: ReqTransPoPurchListPage datasource
It was very simple. It was only necessary to reload the name of the query in the datasource of the form so that everything was updated.
↧
↧
Forum Post: RE: Error when importing general journal transactions using DIXF
I used the wizard without success
↧
Forum Post: RE: Error when importing general journal transactions using DIXF
I am using ledger account type type
↧
Forum Post: RE: Update table index using table extension
It's not a std AX package. We have our own solution build on the Dynamix AX framework with multiple packages (and extensions). So the problem is situated fully in our proper sollution, so that's why we can change the index property itself on the base table. So if you are trying to do the same on a default AX table, i'm afraid it won't be of any help... It would be better if MS would allow to add fields to an existing index in a table extension in my opinion.
↧
↧
Forum Post: RE: Document sharing from mobile to AX using Custom service
I think this is from the client application, not from AX. Try to debug your service class, as recommended above.
↧
Forum Post: RE: opening balance entry import
Hi Imane, You can record the transaction as of 31 Dec 2017 and then run the year end closing process, which will create an opening balance transaction for 01 Jan 2018. Have you tried doing that? Best regards, Ludwig
↧
Forum Post: RE: Error when importing general journal transactions using DIXF
Hello Elie, If you used the wizard, all number sequences should be filled and there should be no gaps in the number sequence sections that can be identified in your previous screenshot. Can you possibly try again and/or test this in a different demo/test system? Best regards, Ludwig
↧
Forum Post: RE: opening balance entry import
but the year 2017 is already closed . can i open it ? how?
↧
↧
Forum Post: RE: opening balance entry import
If December 2017 is just put on hold you can reopen the period However, if it is closed you can't do that. Can you check the period status for 12/2017? Ludwig
↧
Forum Post: RE: Error when importing general journal transactions using DIXF
For effectively using the General Ledger module (in General), you have to Setup a number sequence for all the references, listed in the screenshot shared by Elie Rostom, which can be accessed from the path shared by Taran Randhawa in earlier comments. The number sequence wizard is only used to create a new number sequence. Let's say a sequence that Looks like GenJ###### (which can generate numbers like GenJ000001, GenJ000002........) But "how this new number sequence will be used for General Journal" is a different Thing altogether, which Elie Rostom and Taran Randhawa have very correctly pointed out. The error message you got '...a number sequence reference is missing....' also says this. (A reference missing, not to create a new number sequence)
↧
Forum Post: RE: opening balance entry import
It is open ! But some modifications were done at 31/12/2017 and i dont want them to appear after closing the FY . What can i do please?
↧
Forum Post: RE: How to create or update email template placeholders runtime using x++
I have a similar requirement. Please share code.
↧
↧
Forum Post: VSTS suggestion needed
Hi Friends, When we launch our AX 2012, a vendor did all customization in VAR/1stModelStore, after that, we did ours in CUS/2ndModelStore, later on, we put CUS/2ndModelStore into VSTS, since everything will be in CUS/2stModelStore from now on. Now, we have a problem, since we need to make change in object in 1stModelStore, and we can't check it in to CUS/2ndModelStore, what's best way to handle it, any suggestion is appreciated.
↧
Forum Post: RE: Validate GL Account Structure on Vendor Invoices upon submit to Workflow
Did anyone get an answer to this. Currently setting up workflows and can't believe a supplier invoice is only validated at the end of the workflow, and then just 'stops' if it isn't valid. Is there a solution to this?
↧
Forum Post: RE: Validate GL Account Structure on Vendor Invoices upon submit to Workflow
Hello Jojo19834, I would suggest that you create an idea on the dynamics ideas/experience portal to get this fix because at the moment a system requirement would be required for the check you are looking for. Best regards, Ludwig
↧
Forum Post: RE: Class Hcmworkerlookup sort
Hi Nikolaos, Here is the changed code part in red within updateQuery method in class HCMWorkerLookup, and screen shot of result, nothing else changed. Query 'MyHcmWorkerLookup' is the one I showed in previous screen shot, we joined a table to filter result. public Query updateQuery(HcmWorkerRecId _workerRecId = 0) { QueryBuildRange legalEntityRange; QueryBuildRange validFromRange; QueryBuildRange validToRange; QueryBuildRange workerRange; QueryBuildRange employmentValidFromRange; QueryBuildRange employmentValidToRange; QueryBuildRange employmentTypeRange; QueryBuildDataSource qbdsEmployment; QueryBuildDataSource qbdsDirPersonUser; QueryBuildDataSource qbdsActiveEmployments; QueryBuildDataSource qbdsWorker; utcdatetime now = DateTimeUtil::utcNow(); // My change > if(Mycondition) { query = new Query(queryStr(MyHcmWorkerLookup)); } // my change > qbdsWorker = query.dataSourceTable(tableNum(HcmWorker)); qbdsEmployment = query.dataSourceName('HcmEmployment'); qbdsActiveEmployments = query.dataSourceName('ActiveEmployments'); qbdsDirPersonUser = query.dataSourceTable(tableNum(DirPersonUser)); validFromRange = qbdsEmployment.findRange(fieldNum(HcmEmployment, ValidFrom)); validToRange = qbdsEmployment.findRange(fieldNum(HcmEmployment, ValidTo)); legalEntityRange = qbdsEmployment.findRange(fieldNum(HcmEmployment, LegalEntity)); employmentTypeRange = qbdsEmployment.findRange(fieldNum(HcmEmployment, EmploymentType)); workerRange = qbdsEmployment.findRange(fieldNum(HcmEmployment, Worker)); employmentValidFromRange = qbdsActiveEmployments.findRange(fieldNum(HcmEmployment, ValidFrom)); employmentValidToRange = qbdsActiveEmployments.findRange(fieldNum(HcmEmployment, ValidTo)); ............... Please let me know what else you want to know.
↧
↧
Forum Post: RE: opening balance entry import
Hello Imane, You can create a new closing period for 31/12/2017 and then use a closing sheet to post the transaction on 31/12/2017. Doing this will allow you to identify and separate the transaction from the other ones that you have already recorded. Once this is done, you run the year end closing process again to get your balances transferred to 01 Jan 2018. Best regards, Ludwig
↧
Forum Post: Purchase overdelivery serial number creation
Hello all, We use AX 2012 R3 CU 13. Release product P1 is stocked, tracked by serial number. No serial number group (manual serial number creation. ie no number sequence). Overdelivery setup is completed : Overdelivery accepted in procurement parameters. 50% overdelivery accepted in product P1. I create a PO with a line for P1 of Qty 10. Upon product receipt, Qty of 12 is counted. 12 is set as the received qty in product receipt form (lines). I have to go through the registration process to create serial numbers, but I have not found the way to create more serial numbers than the ordered quantity (10). The top section of the registration form does not allow me to change the quantity. If I add the transaction to the bottom part of the form (register now section), when I try changing the quantity from 10 to 12, the "create serial Numbers" action is disabled. Complementary information : If P1 has a serial number group (automatic serial number creation on receipt), 12 serial numbers get created upon receipt posting when changing received qty from 10 to 12. Any help will be greatly appreciated. Thanks Denis Marcoux
↧
Forum Post: RE: Class Hcmworkerlookup sort
I can't see the screenshot. I still would like to know from where this lookup is called. Standard form? Your own form? I feel you share only part of your process and therefore it's hard to troubleshoot.
↧