Meta tags:

Headings (most frequently used words):

share, this, posts, performance, considerations, abstract, on, ax, 2012, using, sysdictcoder, recent, categories, tags, aggregate, functions, event, handlers, can, define, or, final, methods, table, unexpected, assertion, failure, caused, by, impossible, modification, keeping, an, eye, output, to, files, yet, another, cause, of, logon, errors, inconsistent, behavior, between, and, cil, tables, with, inheritance, editor, extensions, don, forget, the, correct, method, signature, when, runclassmethodil, brace, yourselves, new, are, coming, pagination,

Text of the page (most frequently used words):
the (135), and (57), testquerytableid (54), new (48), 2303 (48), this (37), info (36), real (34), window (31), opens (30), #expected (30), you (29), for (28), run (25), was (22), xppilexecutepermission (22), query (22), share (21), when (21), that (21), print (20), email (20), queryrun (20), tableid (19), static (18), can (17), table (17), but (16), with (16), container (16), fixed (16), dirpartytable (16), prodtable (16), because (15), they (15), not (14), mymethod (14), connull (14), funcname (14), void (14), runxpp (14), runcil (14), performance (14), some (13), method (13), using (13), 2012 (13), abstract (13), error (12), private (12), total (12), categories (11), had (11), get (11), ecoresproduct (11), event (11), posted (10), link (10), friend (10), have (10), tags (10), return (10), were (10), 2015 (10), eht (10), comment (9), are (9), while (9), time (9), like (9), information (9), programming (9), server (9), there (9), tables (9), handlers (9), other (8), from (8), lot (8), runclassmethodil (8), public (8), ret (8), use (8), records (8), maxloops (8), leave (7), 2014 (7), about (7), ax2012 (7), running (7), another (7), only (7), code (7), problem (7), results (7), methods (7), used (6), after (6), could (6), test (6), 2978 (6), dostuff (6), qbds (6), tablenum (6), int (6), simple (6), job (6), caused (6), dynamics (6), group (6), considerations (6), eventhandlertester (6), qtysched (6), next (5), posts (5), has (5), more (5), content (5), decided (5), then (5), axapta (5), correct (5), cil (5), actually (5), which (5), sense (5), values (5), out (5), myclass (5), assert (5), what (5), file (5), january (5), just (5), make (5), field (5), final (5), aggregate (5), page (4), been (4), still (4), quite (4), bit (4), write (4), again (4), made (4), times (4), don (4), _container (4), classstr (4), staticmethodstr (4), codeaccesspermission (4), revertassert (4), going (4), extensions (4), november (4), log (4), now (4), files (4), client (4), ran (4), demo (4), 2975 (4), strfmt (4), setprefix (4), adddatasource (4), couldn (4), related (4), sometimes (4), enough (4), one (4), work (4), data (4), fields (4), any (4), output (4), powershell (4), assertion (4), impossible (4), modification (4), doesn (4), eventhandler (4), functions (4), select (4), wordpress (3), october (3), blog (3), changed (3), someone (3), somehow (3), forget (3), involved (3), writing (3), useful (3), should (3), something (3), discovered (3), find (3), very (3), couple (3), calling (3), object (3), runil (3), type (3), tip (3), makes (3), think (3), way (3), how (3), try (3), really (3), errors (3), editor (3), tool (3), system (3), where (3), yet (3), between (3), inheritance (3), bug (3), same (3), sysdicttable (3), getroottable (3), instances (3), types (3), derived (3), batch (3), turns (3), than (3), customer (3), problems (3), user (3), happy (3), wasn (3), users (3), userinfo (3), defined (3), created (3), also (3), added (3), access (3), partition (3), keeping (3), eye (3), wait (3), temp (3), logfile (3), csv (3), say (3), part (3), quick (3), unexpected (3), failure (3), cus (3), layer (3), project (3), why (3), omoperatingunit (3), even (3), define (3), december (3), scenario (3), main (3), 100000 (3), runwithaotsubscription (3), thedelegate (3), thedelegatemethod (3), runwithdelegatesubscription (3), runwithmethod (3), calls (3), faster (3), sum (3), brace (2), yourselves (2), coming (2), few (2), getting (2), lately (2), dealing (2), often (2), post (2), help (2), coworkers (2), course (2), those (2), paying (2), people (2), documentation (2), tools (2), since (2), started (2), blogging (2), too (2), here (2), understand (2), bonus (2), putting (2), might (2), may (2), signature (2), permission (2), failed (2), runtime (2), step (2), before (2), does (2), know (2), stop (2), them (2), directory (2), inconsistent (2), behavior (2), machine (2), exactly (2), 2377 (2), _params (2), querybuilddatasource (2), break (2), class (2), debugging (2), noticed (2), variable (2), see (2), debugger (2), nothing (2), look (2), came (2), export (2), easier (2), recently (2), fine (2), during (2), different (2), cause (2), logon (2), admin (2), possible (2), mandatory (2), standard (2), record (2), sure (2), language (2), helplanguage (2), createusersessions (2), value (2), both (2), second (2), found (2), worked (2), contact (2), parameter (2), solution (2), jobs (2), things (2), effort (2), path (2), logging (2), 000 (2), infolog (2), want (2), its (2), ax2012r2 (2), aot (2), xpo (2), change (2), ended (2), modifications (2), dimension (2), delete (2), call (2), dimensions (2), empty (2), february (2), throw (2), missingoverride (2), message (2), modifier (2), seems (2), let (2), seen (2), effect (2), ignoring (2), handler (2), noticeable (2), directly (2), worse (2), subscribed (2), args (2), _args (2), without (2), eventing (2), all (2), low (2), difference (2), stuff (2), sysdictcoder (2), proudly, powered, pagination, cleaning, mess, past, days, needs, maintenance, significantly, rid, smell, stale, bits, laughing, matter, will, arrive, shortly, amazement, frustration, insights, progress, attained, took, answer, question, stack, overflow, publicly, document, their, findings, spirit, forward, revive, nice, place, redirect, questions, passed, got, less, mentoring, official, improved, priorities, shifted, stopped, altogether, evernote, keep, track, myself, developer, community, grown, immensely, many, long, hiatus, spend, realized, better, internet, hard, especially, received, links, check, your, creating, example, won, tier, request, perfect, once, avoided, taking, back, thinking, typing, right, exist, variations, remains, confusion, intensifies, minutes, grumbling, hasty, attempts, fix, common, kicks, executing, confused, works, attention, pop, bad, annoyed, installed, reading, developing, immediately, doing, head, over, download, installing, easy, copying, codeplex, confusing, consuming, figure, giving, luckily, called, ways, clicked, looks, version, handles, base, differently, create, concrete, supported, buffers, hypothesis, infamous, small, happening, visual, studio, ecoresdistinctproduct, extraordinary, until, put, longer, trying, down, starting, collect, picked, application, sounds, certainly, fridge, comet, doozy, contacted, having, themselves, product, seemed, development, never, well, add, digging, through, hooray, cross, references, bunch, copied, unknown, reason, gone, invalid, comparing, however, setting, disappeared, peace, productivity, returned, office, everyone, weird, active, import, wizard, already, initial, trouble, accessing, own, account, none, solutions, online, config, stored, procedure, broken, transaction, full, session, start, continues, microsoft, administrator, into, tried, unix, good, off, everything, harder, outside, box, existing, little, tail, blocked, opened, prompt, issued, command, correction, update, rely, fun, view, being, suppose, need, modify, updated, send, default, limit, lines, lose, means, finished, allowed, edit, remove, finally, exported, entire, deleted, imported, restored, behold, deleting, causing, guess, minor, groups, culprit, backing, department, point, fails, checks, contains, represents, descendant, name, autoidentification, today, testing, module, wanted, much, surprise, telling, major, continue, hadn, anyway, else, reported, either, action, environment, didn, dimensionenabledtype, constructforsystemdefinedbytableid, debug, enforce, overrides, old, school, cu7, reproduce, cu8, specified, intended, behaviour, issue, compiler, whitepaper, mentions, declare, anything, case, meaningful, would, conflicting, given, allow, adding, compile, comments, yourself, approach, flawed, late, idea, did, bother, investigating, body, fact, cost, advocating, against, beware, quicker, improvement, though, uses, matters, xppprepostargs, far, worst, looking, tree, fairly, obvious, bookkeeping, internally, trace, parser, interesting, consistent, every, executed, function, lastly, events, themethod, theaothandler, setup, scenarios, performed, measure, overhead, whatever, business, logic, perform, beyond, expectations, widely, despite, potentially, cleaner, design, issues, stick, heads, delegates, boot, demonstrate, worrying, specific, analysis, tuning, important, solve, requirements, must, implemented, processing, ends, heath, death, universe, march, 2016, love, please, risk, insert, deity, choice, original, uncached, display, imagine, grid, form, readable, literally, says, 5000, 252, production, orders, usmf, company, recommend, rewrite, forgot, such, thing, queries, sql, calculating, single, statement, instead, fetching, calculation, reviews, come, across, protect, guilty, best, practice, installation, recent, search, home, menu, widgets, skip,

Text of the page (random words):
ggregate functions when possible it s a low effort low risk change that can make a noticeable difference share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on december 9 2015 march 16 2016 categories dynamics ax axapta programming tags performance x leave a comment on performance considerations aggregate functions performance considerations event handlers lately i ve been involved quite a bit in performance analysis and tuning on ax 2012 it s not only important to solve the customer s requirements but at the same time the solution must be implemented in a way that its processing ends before the heath death of the universe there s are lot to say about performance but for now i ll just stick to a quick heads up about event handlers and delegates and to boot i can demonstrate it without worrying about customer specific information eventing was added to ax 2012 but it s not widely used in the standard code if at all despite the potentially cleaner design i ve seen some instances where it caused some issues i decided to try to measure the overhead caused by eventing ignoring whatever business logic they might perform the results were beyond my expectations my test setup is a simple class with empty methods for different scenarios the test was performed on an ax 2012 r3 demo vm on the method runwithaotsubscription a post event handler is defined that calls theaothandler method runwithdelegatesubscription calls thedelegate to which thedelegatemethod is subscribed using the eventhandler function lastly runwithmethod directly calls themethod without any events in between in main every scenario is executed 100000 times public static void main args _args eventhandlertester eht new eventhandlertester int i int maxloops 100000 for i 1 i lt maxloops i eht runwithaotsubscription eht thedelegate eventhandler eventhandlertester thedelegatemethod for i 1 i lt maxloops i eht runwithdelegatesubscription for i 1 i lt maxloops i eht runwithmethod public static void main args _args eventhandlertester eht new eventhandlertester int i int maxloops 100000 for i 1 i maxloops i eht runwithaotsubscription eht thedelegate eventhandler eventhandlertester thedelegatemethod for i 1 i maxloops i eht runwithdelegatesubscription for i 1 i maxloops i eht runwithmethod using the trace parser i found some interesting results i ran it a couple of times and results were consistent the event handlers subscribed using eventhandler are by far the worst when looking at the call tree it s fairly obvious why there seems to be a lot of bookkeeping going on internally event handlers defined in the aot are an improvement even though it s the only scenario which uses a parameter xppprepostargs this could make matters worse but actually it doesn t and as expected it s still quicker when calling a method directly now why did i bother investigating this because i ve seen the effect of using event handlers on data methods of often used tables even ignoring the body of the event handlers the simple fact of calling the event handler has a noticeable performance cost i m not advocating against the use of event handlers but beware of them when they re part of code involved in a performance problem if you d like to test this yourself you can use the xpo let me know if you have other results or if my approach is flawed it was getting late when i came up with the idea share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on december 4 2015 december 4 2015 categories dynamics ax axapta programming tags ax2012 performance x 4 comments on performance considerations event handlers can t define abstract or final methods on abstract table it seems ax doesn t allow you to use abstract or final on abstract tables when adding abstract public mymethod to an abstract table e g ecoresproduct you get this compile error conflicting access modifier given the error message doesn t really make sense because the only access modifier specified is public i m not sure if this is intended behaviour or an issue with the compiler there s a whitepaper that mentions you can t declare a table as final but it doesn t say anything about the methods in any case a more meaningful error message would help this was discovered on ax 2012 r2 cu7 but we could reproduce it in the ax 2012 r3 cu8 demo machine to enforce overrides on derived tables you can still use the old school method like so public void mymethod throw error error missingoverride funcname public void mymethod throw error error missingoverride funcname share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on february 24 2015 february 24 2015 categories programming tags ax2012 bug x leave a comment on can t define abstract or final methods on abstract table unexpected assertion failure caused by impossible modification today i was testing some modifications in the ax 2012 project module and wanted to delete a test project i had just created much to my surprise i ended up in the debugger on a failed debug assert call in dimensionenabledtype constructforsystemdefinedbytableid ax was telling me there was a major problem with one of the dimensions and the delete couldn t continue i hadn t even changed any of the dimensions and they were empty anyway no one else had reported the problem either the same action still worked fine in another environment it just didn t make sense it turns out the culprit was the backing table for the department dimension omoperatingunit at the point where the assertion fails it checks if the field group autoidentification contains the field that represents the dimension value this should work because omoperatingunit is a descendant of dirpartytable and that table has the name field in the group it s impossible to change that group on omoperatingunit but somehow that group had ended up in the cus layer and was causing problems i can only guess why there were some other minor modifications on the table but nothing related to the field groups since i m not allowed to edit that group on derived tables i couldn t remove it i finally exported the entire table from the aot deleted the object from the cus layer and imported the xpo again this restored the other modification and lo and behold no more field group in the cus layer and no more problems when deleting a project share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on january 26 2015 categories programming tags ax2012r2 x leave a comment on unexpected assertion failure caused by impossible modification keeping an eye on output to files just a quick tip when you want to do some simple logging when jobs are running suppose you need to modify a lot of data and you want to log which records are updated and some other things you could send it to the infolog window but its default limit of 10 000 lines may not be enough and you lose information it also means you get the information after the job has finished for a data correction job i had to update some 20 000 records and couldn t rely on the infolog for output i decided to write the information to a file the fun part is you can use powershell to view content in real time as it s being added to the file so i made the job with logging to a file say c temp logfile csv while the job was running and ax is blocked i opened a powershell prompt and issued this command get content path c temp logfile csv wait get content path c temp logfile csv wait it s the wait parameter that makes it work like tail f on a unix system i think this is a very simple and good enough solution for one off jobs because we can do everything in ax we can make it harder than it should be for things like this sometimes it s easier to step outside the ax box and use existing tools with little effort share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on january 21 2015 january 21 2015 categories programming tags powershell x leave a comment on keeping an eye on output to files yet another cause of ax 2012 logon errors recently i ran into this error when users tried to log on to a second partition a user session on the server could not be created try to start the client again if the problem continues contact the microsoft dynamics ax administrator it s weird because i had just added users with the active directory import wizard they already had access to the initial partition and i had no trouble accessing the second partition with my own account because of that none of the solutions i found online worked the transaction log wasn t full the createusersessions stored procedure wasn t broken and the config file was correct after comparing records in the userinfo table i noticed that the new records had no values in the fields language and helplanguage they are however mandatory fields in ax they re also used in createusersessions after setting a value in both fields the problem disappeared and so peace and productivity returned to the office and everyone was happy well i wasn t happy how is it possible that mandatory fields don t have any values i used a standard ax tool to add the users to the system after digging through the code it turns out hooray for cross references that a bunch of values for the userinfo record are copied from user admin sure enough there was no language or helplanguage defined on that record for some unknown reason those values were gone and caused invalid userinfo records to be created i fixed the data for user admin and never had that problem again now i was happy too share this share on x opens in new window x email a link to a friend opens in new window email print opens in new window print posted on january 19 2015 january 19 2015 categories other tags ax2012 leave a comment on yet another cause of ax 2012 logon errors inconsistent behavior between x and cil using tables with inheritance this one is a doozy recently a customer contacted me because they were having problems running a job they made themselves to export product information it seemed to work fine in the client during development but the results when running in batch were very different starting from a query on ecoresproduct they collect a lot of information and export it to a file which is picked up by another application sounds simple enough it certainly is a lot easier than putting a fridge on a comet what they were trying to do came down to this query new query qbds query adddatasource tablenum ecoresproduct queryrun new queryrun query while queryrun next ecoresproduct queryrun get tablenum ecoresproduct look up information in related tables sometimes using table id query new query qbds query adddatasource tablenum ecoresproduct queryrun new queryrun query while queryrun next ecoresproduct queryrun get tablenum ecoresproduct look up information in related tables sometimes using table id nothing extraordinary going on there until they put it in batch as it turns out ecoresproduct tableid was no longer correct and because of that they couldn t find some related records while debugging i noticed that when running in batch the variable ecoresproduct was actually of type ecoresdistinctproduct i could see it happening in visual studio when running the job in my client and using the x debugger the variable was of type ecoresproduct then it clicked for me it looks like the cil version of the code handles abstract base tables differently it makes sense actually because you can t create instances of abstract types only of derived concrete types in x it is somehow supported for instances of table buffers to be abstract types i decided to test my hypothesis with another infamous table using inheritance dirpartytable i made a small class with a simple method to run a query on the table and get some records from it static container dostuff container _params connull dirpartytable dirpartytable queryrun queryrun query query querybuilddatasource qbds tableid tableid tablenum dirpartytable int i query new query qbds query adddatasource tableid queryrun new queryrun query while queryrun next dirpartytable queryrun get tableid info strfmt expected id 1 real id 2 tableid dirpartytable tableid i if i 5 break return connull static container dostuff container _params connull dirpartytable dirpartytable queryrun queryrun query query querybuilddatasource qbds tableid tableid tablenum dirpartytable int i query new query qbds query adddatasource tableid queryrun new queryrun query while queryrun next dirpartytable queryrun get tableid info strfmt expected id 1 real id 2 tableid dirpartytable tableid i if i 5 break return connull i then called the method in 2 ways server static private void runxpp setprefix funcname testquerytableid dostuff server static private void runxpp setprefix funcname testquerytableid dostuff server static private void runcil container ret xppilexecutepermission xppilexecutepermission setprefix funcname xppilexecutepermission new xppilexecutepermission xppilexecutepermission assert ret runclassmethodil classstr testquerytableid staticmethodstr testquerytableid dostuff connull codeaccesspermission revertassert server static private void runcil container ret xppilexecutepermission xppilexecutepermission setprefix funcname xppilexecutepermission new xppilexecutepermission xppilexecutepermission assert ret runclassmethodil classstr testquerytableid staticmethodstr testquerytableid dostuff connull codeaccesspermission revertassert the results were exactly what i expected info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runxpp expected id 2303 real id 2303 info testquerytableid run testquerytableid runcil expected id 2303 real id 2377 info testquerytableid run testquerytableid runcil expected id 2303 real id 2978 info testquerytableid run testquerytableid runcil expected id 2303 real id 2978 info testquerytableid run testquerytableid runcil expected id 2303 real id 2978 info testquerytableid run testquerytableid runcil expected id 2303 real id 2975 info testquerytableid run testquerytableid runcil expected id 2303 real id 2975 luckily it can be fixed with sysdicttable getroottable info strfmt expected id 1 real id 2 fixed id 3 tableid dirpartytable tableid sysdicttable getroottable dirpartytable tableid info strfmt expected id 1 real id 2 fixed id 3 tableid dirpartytable tableid sysdicttabl...