0
Category:
STATUS DETAILS

Comments

We recently had this issue on an implementation where data entities were not available for detours/mds. It became a massively time consuming task to recreate the steps between environments and would only increase on larger projects. I can see this becoming a bigger requirement in the future as detours/mds are used more often. I believe this should be considered for the roadmap.

Category:

Hi Aleksandar,I can also confirm the same requirement as Durwin explained. This an absolute necessity for Irish customers.All Irish companies doing business in UK must submit their VAT statement to HMRC vis Making Tax Digital (MTD).We used to create customer's instance with GB as location to get the MTD available to the customer. Which is not possible anymore because of Brexit. Because, creating customer's instance with GB location would get Azure Datacentre located in UK. Which is not permitted under EU rule.Therefore, having MTD available for Irish customer has become a necessity now.I can also confirm that no additional modification is required for MTD to work for Irish customer. We have tested this before in old NAV. Taking MTD related objects and deploying in W1 NAV worked.It would really be helpful if you could make MTD available for Irish instances, please.Best Regards,Abdus

Category:

It also overlaps with this Idea as well: https://experience.dynamics.com/ideas/idea/?ideaid=ff2f8696-0f95-ea11-99e5-0003ff68a0e8The dragging and dropping of attachments should be possible in the entire D365 F&SCM solution where attachments are used.

Category:

Allowing users reactivate a lead after 90 days. For example, a lead is currently not interested but in 6 months they may consider it gain. By allowing the user to set the due date of the activity to 6 months the lead remain active for the future date.

Category:

Alot of clients have been asking for this back, now that more and more people are testing out the new look. and its one of those immediate items that make them switch back to the old look. Not sure why Microsoft thought it was a good idea to get rid of this feature, but please add it back. At least for the time being, companies that want to move forward with the new look, you can switch the default view component to the Power Apps Edit/View Component, and you get the option to select all and do color choice fields etc. Looks really good on Work Order view and other areas.

Category:

https://ideas.powerautomate.com/d365community/idea/1711d9ba-3a84-ee11-a81c-6045bdb65d35

Category:

Yes, this is quite handy, if get fixed. especially, where all users are using via web.

Category:

I would like to remind you of this feature request and emphasise how usful it can be: Activities are so important for our users in the context of a company or contact, for example, that we show them as a subgrid on these entities. Under “Related”, they get lost in the hustle and bustle of all linked entities and have to be called up with more clicks. The timeline offers too little space to view activities more intensively at a glance at this place. What users do not understand now is that in contrast to the timeline and the associated view, they can only see directly linked activities on the the subrid. Time and again (most recently today) we have to explain and disappoint users that Microsoft does not allow us to use the "include related" function in subgrids.We now have to replace the subgrid with a canvas app to solve this, which is a lot of effort for us to enable a feature that is actually already there.

Category:

Seems to be a bug and is confusing. You can configure the text in TransactionTexts but the setup is fully ignored.A Change can be easily done by updating the code to the following:Class: TrvExpTableSourceDocument Method: getTransactionTxtAdd the following code before transTxt = transactionTxt.txt(); if (TransactionTextContext::isTypeSupported(LedgerTransTxt::Expense))    {      TransactionTextContext transactionTextContext = TransactionTextContext::newForTransactionType(LedgerTransTxt::Expense); //TransactionTextContextExpense      transactionTextContext.setTableBuffer(_trvExpTrans);      transactionTextContext.setTableBuffer(TrvExpTable::findRecId(_trvExpTrans.TrvExpTable));      transactionTxt.setTransactionTextContext(transactionTextContext);    }    

Category:

Please add the registration No to standard API - customers, vendors, contacts

Category:

  • 1
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 500