Think of a map as an updateable query. Your basically matching up a bunch of tables that hold similiar data, and then providing a common way to interact with the whole group. If a field is shared amongst several tables, then an update to the one field can affect all the relevant tables. Of course, in my mind, they just serve to overcomplicate matters. The addition of yet another layer --- ugh. Beware also that their implementation leaves a lot to be desired. For instance, take SalesPurchLine.salesPurchTable(). Inside the code for this method it references: this.salesPurchtable(). Where is this defined? In one of the tables that the map is based on.....doh!
--- On Sat, 6/28/08, Vamsi Praneeth <[EMAIL PROTECTED]> wrote: From: Vamsi Praneeth <[EMAIL PROTECTED]> Subject: [development-axapta] What are Maps and what's the use of them? To: [email protected] Date: Saturday, June 28, 2008, 8:32 PM Hello guys...I just wanna know...what actually are Maps in Dynamics AX 4.0 what are they used for? I have read in the e-books of Microsoft but couldn't figure out what actually are those.....Can someone explain me in detail what they are? [Non-text portions of this message have been removed]
