0

Background: I'm trying to edit an AX Report in Visual Studio. I have previously been able to create reports in VS and integrate them into AX. But I haven't used this in several weeks. Now, suddenly it doesn't work anymore.

Symptoms: When I open Visual Studio the Application Explorer does not show our actual AOS but instead says "Default (cus) [CUS Model]". update: As it turns out the Application Explorer does connect to the right AOS. It just displays this default name (and now since resetting VS user data is fixated on the USR-layer)

Attempted solutions:

I can't find anything else besides reinstalling everything. I've seen one reference to a KB2827469 that supposedly changes the way Visual Studio loads the AX configuration but can't find anything about that KB on microsoft's websites.

Kempeth
  • 1,856
  • 2
  • 22
  • 37
  • You can find [KB2827469](https://fix.lcs.dynamics.com/Issue/Resolved/1196432?kb=2827469) in the Lifecycle Services Issue Search, it's title is: "Visual Studio .NET launched from within AOT overlooks AxConfig parameter and any custom config profile." – FH-Inway Jul 05 '17 at 13:38
  • Have you tried resetting your VS user data? `/ResetUserData` see https://stackoverflow.com/questions/17203820/how-do-i-truly-reset-every-setting-in-visual-studio-2012 – Alex Kwitny Jul 05 '17 at 14:17
  • @AlexKwitny The only thing this did was change the displayed AOS to "Default (*usr*) [*USR* Model] – Kempeth Jul 05 '17 at 14:28
  • @FH-Inway. Thank you very much for the link. But I can't access it. I don't have the necessary permissions... – Kempeth Jul 05 '17 at 14:29
  • To me this sounds like your very first link about setting the `/AxConfig` in the shortcut is not done correctly. Can you triple-check it? – Alex Kwitny Jul 05 '17 at 16:08
  • I've realized that the Application Explorer actually connects to the right AOS but just displays the wrong name (and is now fixed on the USR layer). The bigger issue is that VS says that the reports in the project don't exist in the repository. I thought the issue described in this question was the cause for my bigger problem. **I'm unsure how to proceed:** should I update the question or start a new one? – Kempeth Jul 06 '17 at 08:24
  • 1
    Answer this question, then create a new question. – FH-Inway Jul 13 '17 at 10:07

0 Answers0