RE: [development-axapta] SysREcordTemplate / creating new item
Hi Karsten The record template feature in 3.0 is activated automatically by the kernel on all tables that have the type Main. All you need to do is: 1. right click on a record for instance in the inventory table 2. choose record info 3. select company accounts template or user template 4. save with a name 5. go into the item table again press Ctrl+N, and you will get a template selection form up you can choose from 6. In basic/setup/record templates you can see what templates are in the system and which are active on which tables. Here you can also specify default templates. Best regards Mai-Britt From: Karsten Krabbes [mailto:[EMAIL PROTECTED] Sent: 15. juni 2004 11:21 To: [EMAIL PROTECTED] Subject: [development-axapta] SysREcordTemplate / creating new item Hi all, from Version 2.5 to 3.0 MBS introduced the RecordTemplate Model. Has anybody a clue how to get the information stored there back ? I want to create a new item and set all the default parameters (in 2.5 they where in Table InventParameters). How can I do that ? br Karsten Yahoo! Groups Sponsor ADVERTISEMENT click here http://us.ard.yahoo.com/SIG=129t1silf/M=295196.4901138.6071305.3001176/ D=groups/S=1705006764:HM/EXP=1087378156/A=2128215/R=0/SIG=10se96mf6/*htt p:/companion.yahoo.com http://us.adserver.yahoo.com/l?M=295196.4901138.6071305.3001176/D=group s/S=:HM/A=2128215/rand=807783625 Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] be * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . [Non-text portions of this message have been removed] Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
SV: [development-axapta] OCX error while connecting to server on client machine
Hi Pankaj If you experience a problem with Axapta where you would like to request assistence from Microsoft Business Solutions, you will have to contact your respective country office. This mailing group is not sponsored or monitored directly by Microsoft Business Solutions. It is a community, where you find piers working with Axapta. Most likely another pier will be able to assist you in the matter, due to their vast experience working with Axapta. Best regards Mai-Britt Fra: Pankaj Kumar Sil [mailto:[EMAIL PROTECTED] Sendt: ma 19-04-2004 14:28 Til: [EMAIL PROTECTED] Emne: [development-axapta] OCX error while connecting to server on client machine I would like to put the technical problem to Microsoft which we are facing while accessing Axapta production environment: Environment: 1] Database server SQL 2000 Cluster [Active/Passive] on Windows 2000/SP4 2] one AOS server 3.0 with axapta application 3.0, Axapta client 3.0 installed on same server with SP2 [on Windows 2000/SP4]. 3] Axapta Client with SP2 [On Windows 2000 Professional/Windows XP]. When we install Axapta 3.0 client on new PC, after applying SP2 it has been configured to connect to AOS and access Axapta application on production environment. After we log on to Axapta we get following error The client installation is missing the required files to run Navision Axapta Click ok to install now. When we client on OK we get following error: Error Message (14:15:56) File 'C:\Axapta 3.0 \Client\share\include\TDSOLClockControl.ocx' could not be opened. Error Message (14:15:56) File 'C:\Axapta 3.0 \Client\share\include\CCLicens.lic' could not be opened. Error Message (14:15:56) File 'C:\Axapta 3.0 \Client\share\include\ctyear.ocx' could not be opened. I have also went to technet sites to find about this problem and already tried: 1] copying application and client software in same directory at client PC. 2] Manually registering application server OCX files to register at client PC by using Regsvr32 command. 3] Checking the permission on client directory for full access. Still the problem is same. Please find snapshots of the error for your preview attached herewith. Important to note that when we access this same client from AOS server itself, we do not get any error. Let me know if you need more information. Thanks in Advance Regards, Rajesh Mehta Rajesh Mehta MCSE,CCNA,CCA,CTC Network Consultant SDI Technologies HP:081586150072 www.sdiworld.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
SV: [development-axapta] Record template
Hi Eva Det standard record templates provided with Axapta - are triggered from the Axapta kernel - the table must be of type main table in order to ensure that the feature is triggered with Ctrl+N. Best regards Mai-Britt Fra: Aksnes Eva [mailto:[EMAIL PROTECTED] Sendt: ti 06-04-2004 15:28 Til: [EMAIL PROTECTED] Emne: RE: [development-axapta] Record template Nice, but... Was thinking about the templates that are saved in the system. SysRecordTemplate - thing. The ones you can choose from the SysRecordTemplateSelect - form. Eva Aksnes -Original Message- From: Theissen, Annette [mailto:[EMAIL PROTECTED] Sent: 6. april 2004 15:18 To: '[EMAIL PROTECTED]' Subject: AW: [development-axapta] Record template Have a look at this example. VendTable tabOrig, tabCopy; ; tabCopy = tabOrig.data(); // Make some modifications at least change the primary key ;-) tabCopy.insert(); I hope this could help you! Bye, Annette -Ursprüngliche Nachricht- Von: eva_aksnes [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 6. April 2004 13:39 An: [EMAIL PROTECTED] Betreff: [development-axapta] Record template Is it possible to use a recordtemplate from code - to make a new customer or project or item? How? Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. winmail.dat
RE: [development-axapta] Disabling dimension values...
Hi Peter You will find that for Axapta version 4.0 a new concept called hierarchical dimensions will be introduced - apart from being able to have dimension hierarchies, you will also be alble to work with validation rules for dimensions - thereby also allowing you to block a dimension completely for entires. Best regards Mai-Britt From: Peter Chalem [mailto:[EMAIL PROTECTED] Sent: Tue 23-03-2004 18:52 To: [EMAIL PROTECTED] Subject: [development-axapta] Disabling dimension values... Hi everyone We have a request from a customer and we think is a valid business request, so we want to find out if the option already exist or if someone knows how to do this Suppose I'm using a dimension as a cost center with the following values: - Management - Sales - Production - Human Resource - Inventory - Purchasing ... I already have records and transactions with all the above cost centers, and I decide that I'm dividing my Sales cost center into Marketing, Corporate Sales and Retail Sales so I need to have only the following centers... - Management - Marketing - Corporate Sales - Retail Sales - Production - Human Resource - Inventory - Purchasing ... as you can see the Sales cost center is no longer in use ... so the question is: - How do I disable a cost center(or any other value from any Dimension), so it cannot be used in the system anymore for future transactions? - How do I know where is the cost center being used in parametrization (customers, suppliers, products, ledger accounts, etc)? Thanks and regards Peter Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. winmail.dat
RE: Re-2: [development-axapta] Mutli-Country Implementation - Single Database
Hi Jesper Good question. The essential difference between the DIS and the LOS layers is the fact that normally only country specific legal demands and common practice (that is a must in the country) should be made in the DIS layers. Since a release takes about 1,5 years to make we need to be able to react quickly when legal demands are not met in the countries that is why we release DIS layers. The LOS layers are localized solutions and more specific, and that makes it a bit difficult just to merge them into the standard. I think you will find that we will focus greatly on merging all DIS layers just now when a similar process for the LOS layers will apply I am not able to tell. Best regards Mai-Britt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 4. marts 2004 09:55 To: [EMAIL PROTECTED] Subject: Re-2: [development-axapta] Mutli-Country Implementation - Single Database Hi Mai-Britt, Now we are talking about DIS Layers. Are you planning a similar procedure for the LOS layers? /Jesper Original Message processed by Tobit InfoCenter Subject: RE: [development-axapta] Mutli-Country Implementation - Single Database (04-Mrz-2004 9:36) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Mai-Britt, To make sure I have understoodit correctly I 1. When a new service pack is released are the DIS layers merged into the SYS layers? 2. When a new release is issued I understand that most of the DIS layer functionality will be merged into the SYS layer, but some functionality will have to be issued in a DIS layer by the respective country. That means there is some kind of a selection process of what will be merged into the SYS layer and what not. 3. Ifan error has been detected in a DIS layer, like thecontactpersonname example, should a country release a new DIS layer or issue a DIP layer. The question is also related to what should we install when we find a DIS, DIP SP1 and DIP SP2 layer. For example in case of the Dutch localizations. Do we have to install all of them or can we just sustain with the latest DIP layer. Last question I have is about the Russian DIS layer. If you look into a standard Axapta 3.0 version you do not see Russia below the country configuration keys. Nor is it available in the license information as one of the languages. Am I correct when I assume that the moment I have installed the Russian DIS layer these keys become available. Regards, Danny Gaethofs Mai-Britt Winther (MICROSOFT BUSINESS SOLUTIONS) [EMAIL PROTECTED] wrote: Hi Danny For version 4.0 you will expect to find the vast majority of the DIS layers merged into the SYS layer. And as a new thing we are actually striving to deliver all layers at the same time - that means there will not be a 3 months interval between the SYS release and the DIS layers release. I cannot promise you that this will happen for Service pack 3 as well, but I know that all our country offices are actually also trying to meet the service pack 3 release date as well. They are now in the development loop together with the rest of the development team. In the case of the contact person name field - please check the fix list for service pack 2, because the change was actually made for CRM, as far as I remember. That case is unfortunately a classical example of unfortunate events - because normally corrections like that should not be made in a service pack. However there were some problems that needed to be fixed. Normally all country offices do a walk through of the corrections for the service pack and test with their respective DIS layers in order to ensure that these things do not conflict with other DIS corrections - that happens before fx. the service pack is critical test completed. If the country office finds some issues they release a newer DIS layer that will take care of the problems. When building a major release the development circle is long and very tedious. And there are many rules to apply by, however we need to build the whole version, and run a side track for the DIS layers, because some of the DIS layers functionality will have to either be changed or singled out as we develop along. As you all know Axapta strives towards generic design, meaning if a new taxation rule suddenly comes up in fx. Germany and the German office creates a temp. solution in a DIS layer to comply with the legal demand (of course they will try to provide the correct solution from the beginning allowing us just to `plug' it in later in the release), we will have to investigate what it takes to build it in with the standard taxation engine - only separating it with a configuration key. You may probably not expect that all DIS layers will be merged to the SYS layer in 4.0 - especially
RE: [development-axapta] Mutli-Country Implementation - Single Database
specific functionality is linked to a configuration key. A configuration key can be switched on or off for the whole application (i.e. for all companies). So, you should switch on all keys for all countries you have. In the code, they check if a configuration key is enabled to execute code. This implies that in an installation with Belgian and Dutch functionality the functionality for both countries will be executed, and not one of them. Of course, this implies that modifications are still necessary, even if layers have been integrated. Seems we still have a long way to go. Gert Neetesonne EDAN Business Software _ From: Mai-Britt Winther (MICROSOFT BUSINESS SOLUTIONS) [mailto:[EMAIL PROTECTED] Sent: zaterdag 28 februari 2004 13:51 To: [EMAIL PROTECTED] Subject: SV: [development-axapta] Mutli-Country Implementation - Single Database Hi Danny MBS developement is for every major version merging existing DIS layers - however you will find that for example the Russian DIS layer is a tricky layer to merge, since that layer i huge. All other layers will try to keep their pieces of country specific functionality to a bare minimum thereby enabling us to easier merge these pieces into a new version. Having written this - we have a team at MBS who is concentrating on merging these DIS layers into the next major release - in this case 4.0. However in the meantime, partners would have to merge the DIS layers themselves, if they require and choose to run with more than one DIS layer on the same installation. Best regards Mai-Britt _ Fra: origaet [mailto:[EMAIL PROTECTED] Sendt: lø 28-02-2004 13:35 Til: [EMAIL PROTECTED] Emne: [development-axapta] Mutli-Country Implementation - Single Database Dear all, I am investigating how a world-wide roll-out of Axapta can be established using one central database. The biggest problem I see at current is related to the Country Specific layers, whereas these are developed by each MBS Country Team. Possibly, whithout having it investigated, these country layers can have contradictionary approaches. Most likely, there are country layers that have upgraded the database with new fields and even tables. In previous topics I read suggestions that the different country layers (DIS, DIP) should be merged. If however the database schemes are different between country layers merging the layers will results in greater inconsistencies. Having to investigate all the different layers to find out what is matching and what not, and thereafter perhaps applying all the differences to one base country layer becomes unfeasible. I recognize two possible situations. Situation 1 If database schemes are identical, one could consider installing an application for each layer. Situation 2 If database schemes are different, one will have to patch all the country layers into one big layer. Apply the database changes made by every country to the central database, validate all the country application layers, and hope all of it works. I have a few questions about the subject: 1. Is there some kind of standardized development rule to avoid two or more countries apply similar - but not precise the same - database changes. Maybe by giving each country seperate ranges for naming tables, fields, etc... 2. What experiences do we have with inconsistencies between different country layers - especially database schemes. 3. In case of situation 1 is there a way to use one central application. I am thinking about determing the country layer to use based on logon parameters. 4. Are there more issues besides the country layers that should be investigated thoroughly for this kind of roll-out. 5. Is MBS planning to do some about this problem, for at least the aim is to also cover global companies. All information is welcome! Kind Regards Danny Gaethofs Yahoo! Groups Sponsor ADVERTISEMENT http://rd.yahoo.com/SIG=12c63lig6/M=274551.4550177.5761904.1261774/D=egroup web/S=1705006764:HM/EXP=1078058127/A=2019528/R=2/SIG=141cnn6h7/*http:/ad.dou bleclick.net/jump/N3349.yahoo1/B1282054.27;abr=!ie4;abr=!ie5;sz=300x250;code =18634;dcopt=rcl;ord=1077971727683696? Click HereClick Here _ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . ATTACHMENT part 2 application/ms-tnef name=winmail.dat Do you Yahoo!? Yahoo! Search - Find what youre looking for faster. Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
SV: [development-axapta] Mutli-Country Implementation - Single Database
Hi Danny MBS developement is for every major version merging existing DIS layers - however you will find that for example the Russian DIS layer is a tricky layer to merge, since that layer i huge. All other layers will try to keep their pieces of country specific functionality to a bare minimum thereby enabling us to easier merge these pieces into a new version. Having written this - we have a team at MBS who is concentrating on merging these DIS layers into the next major release - in this case 4.0. However in the meantime, partners would have to merge the DIS layers themselves, if they require and choose to run with more than one DIS layer on the same installation. Best regards Mai-Britt Fra: origaet [mailto:[EMAIL PROTECTED] Sendt: lø 28-02-2004 13:35 Til: [EMAIL PROTECTED] Emne: [development-axapta] Mutli-Country Implementation - Single Database Dear all, I am investigating how a world-wide roll-out of Axapta can be established using one central database. The biggest problem I see at current is related to the Country Specific layers, whereas these are developed by each MBS Country Team. Possibly, whithout having it investigated, these country layers can have contradictionary approaches. Most likely, there are country layers that have upgraded the database with new fields and even tables. In previous topics I read suggestions that the different country layers (DIS, DIP) should be merged. If however the database schemes are different between country layers merging the layers will results in greater inconsistencies. Having to investigate all the different layers to find out what is matching and what not, and thereafter perhaps applying all the differences to one base country layer becomes unfeasible. I recognize two possible situations. Situation 1 If database schemes are identical, one could consider installing an application for each layer. Situation 2 If database schemes are different, one will have to patch all the country layers into one big layer. Apply the database changes made by every country to the central database, validate all the country application layers, and hope all of it works. I have a few questions about the subject: 1. Is there some kind of standardized development rule to avoid two or more countries apply similar - but not precise the same - database changes. Maybe by giving each country seperate ranges for naming tables, fields, etc... 2. What experiences do we have with inconsistencies between different country layers - especially database schemes. 3. In case of situation 1 is there a way to use one central application. I am thinking about determing the country layer to use based on logon parameters. 4. Are there more issues besides the country layers that should be investigated thoroughly for this kind of roll-out. 5. Is MBS planning to do some about this problem, for at least the aim is to also cover global companies. All information is welcome! Kind Regards Danny Gaethofs Yahoo! Groups Sponsor ADVERTISEMENT Click HereClick Here http://rd.yahoo.com/SIG=12c63lig6/M=274551.4550177.5761904.1261774/D=egroupweb/S=1705006764:HM/EXP=1078058127/A=2019528/R=2/SIG=141cnn6h7/*http://ad.doubleclick.net/jump/N3349.yahoo1/B1282054.27;abr=!ie4;abr=!ie5;sz=300x250;code=18634;dcopt=rcl;ord=1077971727683696? Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ . Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. winmail.dat
RE: [development-axapta] Installing Axapta and Applying Service Packs
Hi Bob When running the installation portal for every service pack you will find the relevant information in order to upgrade to a service pack. Axapta 3.0 installation portal has a guide to help install the product as well. Best regards Mai-Britt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 23. februar 2004 15:12 To: [EMAIL PROTECTED] Subject: RE: [development-axapta] Installing Axapta and Applying Service Packs Hi All, I am trying to find a good document on Installing Axapta and applying Service Packs 1, 2 3. etc. The documet I have for install does not seem to be current and I have nothing on Service Packs. Any help will be greatly appreciated. Thank you, Bob Bob Brinker Oakdene Group, Inc. 2625 Butterfield Rd. (Suite 212E) Oak Brook, IL 60523-1261 (630)368-1046 x/230 (630)368-1050 (Fax) [EMAIL PROTECTED] Yahoo! Groups Sponsor ADVERTISEMENT Click Here Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [development-axapta] Upgrade documentation
Hi Jack If you visit the Axapta technet you will find a document published a few months ago by us describing the dos and donts of upgrading in Axapta. Best regards Mai-Britt From: Jack Schilder [mailto:[EMAIL PROTECTED] Sent: 18. februar 2004 23:42 To: [EMAIL PROTECTED] Subject: [development-axapta] Upgrade documentation Hi everyone, In this year 4th year of my study, a (bachelor) paper has to be written. As a former intern at an MBS partner, Axapta seemed a logical choice to write about. The titel of my paper will be: Framework for upgrading to new Axapta releases. In this particular company,there are no specific upgrade-manuals. Only one programmer knows how to do an upgrade, and he does it mainly by heart. He said it's an 'hands-on job'. Maybe, but structured documents are needed for this process. A lot of problems occur during and due to these upgrades, obviously most of these problems ocur with the non-standard axapta programming. My question to you people: Do you have these kind of update manuals in your company, like detailed checklist? And if so would it be possible for me to see them? Has Microsoft shared documents with you that helped with the upgrade? With kind regards, Jack Schilder, student at the Amsterdam Business School Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [development-axapta] PriceAgreements on ItemReq
Hi Eva The item requirement type in sales order is only available for project. It was introduced in version 3.0 in order for the user to be able to packing slip update an item requirement on eg. An internal or fixed-price project (these project do not allow normal invoicing however a lot of customers would prefer to receive a packing slip). Project can only handle standard price agreements in conjunction with a standard sales order on a time-and material project, and that is due to the fact that when creating a sales order line the initialisation of the price discounts will be made this is not done in the same manor for an item requirement. Best regards Mai-Britt From: eva_aksnes [mailto:[EMAIL PROTECTED] Sent: 10. februar 2004 16:05 To: [EMAIL PROTECTED] Subject: [development-axapta] PriceAgreements on ItemReq For some reason priceagreements is not used on salesorders of type ItemReq. I'm looking in to it, to may be able to fix it, but it seems complex. Have any of you tried to do that? Can you think of any reason not to use priceagreements on ItemReqs? I've seen that even though I am able to set the price and linedisc from priceagreements, only the price is on the invoice. The linedisc is completly ignored. I also - was able to tell that the reason for that, is that ItemReq uses ProjTransItem returns 0 on ItemReq (se InitFromProposal on ProjInvoiceItem). I picked up the linedisc and linepersent from the inventtransid, overriding the linedisc and the linepersent-methods on ProjTransItemTrans. Any sideeffects to this stunt that you know of? Anyway - now I can see the linedisc on the invoice - but still the amount is wrong. So now I am looking into changing the amount. I just want some feedback on: am I going about this in a good way? Have you got other suggestions? Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [development-axapta] Print original or copy numberofpages
Hi You have to check the print management parameters set up in sales orders. I original is zero nothing will be printed, only an update will be made. Best regards Mai-Britt From: Cenk Ince [mailto:[EMAIL PROTECTED] Sent: 8. januar 2004 10:53 To: [EMAIL PROTECTED] Subject: [development-axapta] Print original or copy numberofpages Hi all; In axapta 3.0 there is a problem that when i try to have a packingSlip report for a sales order, it says report is empty. But the status of sales order bocomes Delivered. When i debug the code i can see that in custPackingSlipJour table, PrintCopies and PrintPages fields are both 0. So it does not print any pages. Any solutions ? Thanks.. Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to: [EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/development-axapta/ To unsubscribe from this group, send an email to:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [development-axapta] Employee absence registration
You must ensure that an absence setup has been assigned to the employee record. Employee table/tab Employment/ Field group Absence _ From: my_ag [mailto:[EMAIL PROTECTED] Sent: 19. november 2003 05:03 To: [EMAIL PROTECTED] Subject: [development-axapta] Employee absence registration Hi, I need help from HR expert. I run mass creation for absence journal, but none was created for my employees. I get the message no open absence journal exist whenever i tried to create a absence registration. What is the pre-requisite setup to create open absence journals??? Please help. thanks, ag Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Yahoo! Groups Sponsor ADVERTISEMENT Click to learn more... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
RE: [development-axapta] Documenthandling Upgrade 3.0 SP 2
When you upgrade to 3.0 it is essential that you actually run the initialization of the help wizard whether or not you select any languages the wizard must be run/finished. There is a check built in at the end of the wizard to ensure that document handling is activated, when the whole upgrade wizard has completed. You can always re-run the script from Administration/Setup/System/Check-lists/Upgrade check list Best regards Mai-Britt _ From: elianill [mailto:[EMAIL PROTECTED] Sent: 18. december 2003 09:47 To: [EMAIL PROTECTED] Subject: [development-axapta] Documenthandling Upgrade 3.0 SP 2 Hi, Documenthandling with upgraded 2.5 database does not work anymore. The icon in menubar is always deactivated although all settings were checked twice. When opening same application with a not upgraded database with same settings in parameters and user-options it works perfectly. Any help appreciated, thanks a lot! Eli _ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. _ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
