That documentation is incomplete. I have worked with an experienced IT professional to attempt to set this up with no luck. I also reached out to our IFS partner about this. They don’t know. IFS, it is time to provide complete documentation on setting this up. Someone at IFS knows how to do this, they need to document it.
Wow, this is great! Thank you so much Krzysztof!
Would be nice if IFS posted some documentation on this configuration. I asked support, they sent me to consultancy services, consultancy services sent me to my implementation partner. They don’t know. I pay for platinum support. #momentofservice.
I am looking for this functionality too. We are on 23R1, but can’t get it to work. Worked with my partner, no luck. Asked support, they told me to open a consultancy ticket because they don’t support implementing features, opened a consultancy ticket and they forwarded it on to my partner without communicating with me in any way. #momentofserviceGuessing that someone at IFS knows how to configure this. Would be nice if they would share their knowledge.
It is amazing to me how much they talked about being “evergreen” at the IFS Connect conference, but the process to do so is so incredibly convoluted. Time for some significant investment to simplify the upgrade process. Documentation is obviously written by engineers. Completely accurate, but minimally useful.
Gotcha. Found it. Getting to know IFS and was told that pages with the same name in different paths were the same. Have to say that the UX of IFS is less than stellar. Still in our implementation phase, so lots of learning to do.
Matt, your Superhero title is appropriate. That is exactly what I am looking for. Unfortunately it appears I don’t have access to that with my normal admin login. Checked my IFS Admin User account and it doesn't have access either. Will check with support on what I need to get access to that. Thank you so much!
I would also like to not have all of these units of measure active in our system. As to why, I prefer to configure the system in such a way as to limit the mistakes that our users can make. I am pretty sure my business will never use an AU (Astronomical Unit), or the bulk of the other units included in IFS. However, if they are included in there, it makes it more difficult for our part creators to know what part numbers they should be using. Some people respond to this with “just document what UoMs you are using” however, why would I want my users to have to browse to a document to verify something the system can help them with. Providing my users with fewer choices reduces mistakes, simplifies training and reduces documentation. I appreciate your comment about changing system defined parameters causing issues, but I would suggest we be given the ability to inactivate something vs. deleting it. If the particular parameter is needed down the line, the update should check to see if it i
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
